From: Zac Dover Date: Sun, 10 Aug 2025 11:04:44 +0000 (+1000) Subject: doc/cephfs: edit troubleshooting.rst X-Git-Tag: v20.1.1~91^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=cedb26cbf921bc51f6dba658667542a10e7752d8;p=ceph.git doc/cephfs: edit troubleshooting.rst Edit the section "Kernel Mount Debugging" in the file doc/cephfs/troubleshooting.rst. Signed-off-by: Zac Dover (cherry picked from commit 012d38c89583667679d434d6ee2cf2d205ea4501) --- diff --git a/doc/cephfs/troubleshooting.rst b/doc/cephfs/troubleshooting.rst index 79e6682d1abed..4960bb4ac08fb 100644 --- a/doc/cephfs/troubleshooting.rst +++ b/doc/cephfs/troubleshooting.rst @@ -311,10 +311,17 @@ If you suspect a potential monitor issue, enable monitor debugging as well Kernel mount debugging ====================== -If there is an issue with the kernel client, the most important thing is -figuring out whether the problem is with the kernel client or the MDS. Generally, -this is easy to work out. If the kernel client broke directly, there will be -output in ``dmesg``. Collect it and any inappropriate kernel state. +The first step in diagnosing and repairing an issue with the kernel client is +determining whether the problem is in the kernel client or in the MDS. If the +kernel client itself is broken, evidence of its breakage will be in the kernel +ring buffer, which can be examined by running the following command: + +.. prompt:: bash # + + dmesg + +Find the relevant kernel state. + Slow requests -------------