RepoMirrors/ceph
1
0
Fork 0
mirror of https://github.com/ceph/ceph synced 2025-01-29 22:43:40 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc: add a short thing on kernel client troubleshooting.

Browse Source 
I just noticed this sitting uncommitted in my tree.

Signed-off-by: Greg Farnum <gregory.farnum@dreamhost.com>
This commit is contained in:
Greg Farnum 2012-03-19 13:20:40 -07:00
parent de86763213
commit d0ba27ae50
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/dev/kernel-client-troubleshooting.rst Normal file
View File

@ -0,0 +1,17 @@
============
Kernel client troubleshooting (FS)
============
If there is an issue with the cephfs kernel client, the most important thing is
figuring out whether the problem is with the 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 appropriate kernel state. If
the problem is with the MDS, there will be hung requests that the client
is waiting on. Look in /sys/kernel/debug/ceph/*/ and cat the mdsc file to
get a listing of requests in progress. If one of them remains there, the
MDS has probably "forgotten" it.
We can get hints about what's going on by dumping the MDS cache:
ceph mds tell 0 dumpcache /tmp/dump.txt
And if high logging levels are set on the MDS, that will almost certainly
hold the information we need to diagnose and solve the issue.