Re: How to identify MDS client failing to respond to capability release?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



For sufficiently recent clients we do this for you (clients send some metadata like hostname, which is used in the MDS to generate an easier-to-understand identifier).

To do it by hand, use the admin socket command "ceph daemon mds.<id> session ls" command, and look out for the client IP addresses in the address part of each entry. By the way, there have been various other bugs in 3.13-ish kernels, so you should consider using either a more recent kernel or a fuse client.

John

On 30/07/15 08:32, Oliver Schulz wrote:
Hello Ceph Experts,

lately, "ceph status" on our cluster often states:

    mds0: Client CLIENT_ID failing to respond to capability release

How can I identify which client is at fault (hostname or IP address)
from the CLIENT_ID?

What could be the source of the "failing to respond to capability release" -
Linux kernel on the client too old? We use ceph-0.94.2 on the cluster,
and the CephFS kernel client on the clients (kernel 3.13.0 on Ubuntu 12.04
and Ubuntu 14.04). But it's possible that there's a machine with an
older Kernel around somewhere ...


Cheers and thanks,

Oliver
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux