On Thu, Sep 10, 2015 at 7:44 AM, Shinobu Kinjo <skinjo@xxxxxxxxxx> wrote: >>> Finally the questions: >>> >>> a./ Under a situation as the one describe above, how can we safely terminate >>> cephfs in the clients? I have had situations where umount simply hangs and >>> there is no real way to unblock the situation unless I reboot the client. If >>> we have hundreds of clients, I would like to avoid that. >> >> In your procedure, the umount problems have nothing to do with >> corruption. It's (sometimes) hanging because the MDS is offline. If >> the client has dirty metadata, it may not be able to flush it until >> the MDS is online -- there's no general way to "abort" this without >> breaking userspace semantics. Similar case: >> http://tracker.ceph.com/issues/9477 >> >> Rebooting the machine is actually correct, > > So far, it might be ok, kind of but we have to improve this kind of un-friendly > situation. > We must give more choices to users using more nice messages, or by implementing > another monitor process. Yes, agreed. We may not be able to change the underlying OS rules about filesystems, but that doesn't mean we can't add other mechanisms to make this better for users. John _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |