@@ -319,28 +319,33 @@ output in ``dmesg``. Collect it and any inappropriate kernel state.
319319Slow requests
320320-------------
321321
322- Unfortunately the kernel client does not support the admin socket, but it has
323- similar (if limited) interfaces if your kernel has debugfs enabled. There
324- will be a folder in ``sys/kernel/debug/ceph/ ``, and that folder (whose name will
325- look something like ``28f7427e-5558-4ffd-ae1a-51ec3042759a.client25386880 ``)
326- will contain a variety of files that output interesting output when you ``cat ``
327- them. These files are described below; the most interesting when debugging
328- slow requests are probably the ``mdsc `` and ``osdc `` files.
329-
330- * bdi: BDI info about the Ceph system (blocks dirtied, written, etc)
331- * caps: counts of file "caps" structures in-memory and used
332- * client_options: dumps the options provided to the CephFS mount
333- * dentry_lru: Dumps the CephFS dentries currently in-memory
334- * mdsc: Dumps current requests to the MDS
335- * mdsmap: Dumps the current MDSMap epoch and MDSes
336- * mds_sessions: Dumps the current sessions to MDSes
337- * monc: Dumps the current maps from the monitor, and any "subscriptions" held
338- * monmap: Dumps the current monitor map epoch and monitors
339- * osdc: Dumps the current ops in-flight to OSDs (ie, file data IO)
340- * osdmap: Dumps the current OSDMap epoch, pools, and OSDs
341-
342- If the data pool is in a NEARFULL condition, then the kernel cephfs client
343- will switch to doing writes synchronously, which is quite slow.
322+ Unfortunately, the kernel client does not provide an admin socket. However,
323+ the the kernel on the client has `debugfs
324+ <https://docs.kernel.org/filesystems/debugfs.html> `_ enabled, interfaces
325+ similar to the admin socket are available.
326+
327+ Find a folder in ``/sys/kernel/debug/ceph/ `` with a name like
328+ ``28f7427e-5558-4ffd-ae1a-51ec3042759a.client25386880 ``.
329+ That folder contains files that can be used to diagnose the causes of slow requests. Use ``cat `` to see their contents.
330+
331+ These files are described below. The files most useful for diagnosis of slow
332+ requests are the ``mdsc `` (current requests to the MDS) and the ``osdc ``
333+ (current operations in-flight to OSDs) files.
334+
335+ * ``bdi ``: BDI info about the Ceph system (blocks dirtied, written, etc)
336+ * ``caps ``: counts of file "caps" structures in-memory and used
337+ * ``client_options ``: dumps the options provided to the CephFS mount
338+ * ``dentry_lru ``: Dumps the CephFS dentries currently in-memory
339+ * ``mdsc ``: Dumps current requests to the MDS
340+ * ``mdsmap ``: Dumps the current MDSMap epoch and MDSes
341+ * ``mds_sessions ``: Dumps the current sessions to MDSes
342+ * ``monc ``: Dumps the current maps from the monitor, and any "subscriptions" held
343+ * ``monmap ``: Dumps the current monitor map epoch and monitors
344+ * ``osdc ``: Dumps the current ops in-flight to OSDs (ie, file data IO)
345+ * ``osdmap ``: Dumps the current OSDMap epoch, pools, and OSDs
346+
347+ If the data pool is in a ``NEARFULL `` condition, then the kernel CephFS client
348+ will switch to doing writes synchronously. Synchronous writes are quite slow.
344349
345350Disconnected+Remounted FS
346351=========================
0 commit comments