On Mon, Apr 24, 2017 at 2:53 PM, Phil Lacroute <lacroute@xxxxxxxxxxxxxxxxxx> wrote: > 2017-04-24 11:30:57.058233 7f5512ffd700 1 -- 192.168.206.17:0/3282647735 > --> 192.168.206.13:6804/22934 -- osd_op(client.4375.0:3 1.af6f1e38 > rbd_header.1058238e1f29 [call rbd.get_size,call rbd.get_object_prefix] snapc > 0=[] ack+read+known_if_redirected e27) v7 -- ?+0 0x7f54f40077f0 con > 0x7f54f40064e0 You can attempt to run "ceph daemon osd.XYZ ops" against the potentially stuck OSD to figure out what it's stuck doing. -- Jason _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com