RepoMirrors
/
ceph
mirror of https://github.com/ceph/ceph
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge PR #19142 into master 

* refs/pull/19142/head:
	doc/dev/kernel-client-troubleshooting: Add kernel dynamic debuggin

Reviewed-by: Sage Weil <sage@redhat.com>
Reviewed-by: Amit Kumar <amitkuma@redhat.com>
This commit is contained in:
Sage Weil 2018-10-30 17:18:06 -05:00
parent c71e993343 37046600f2
commit 860ad1f61c
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/dev/kernel-client-troubleshooting.rst
View File

@ -7,11 +7,15 @@ 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
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.
You can also enable dynamic debug against the cephfs module.
See:
https://github.com/ceph/ceph/blob/master/src/script/kcon_all.sh