Hi,
trying to "umount" a formerly mounted ceph filesystem that has become
unavailable (osd crashed, then msd/mon were shut down using
/etc/init.d/ceph stop) results in "umount" hanging forever in
"D" state.
Strangely, "umount -f" started from another terminal reports
the ceph filesystem as not being mounted anymore, which is consistent
with what the mount-table says.
The kernel keeps emitting the following messages from time to time:
Jun 16 17:25:29 gitega kernel: ceph: tid 211912 timed out on osd0, will reset osd
Jun 16 17:25:35 gitega kernel: ceph: mon0 10.166.166.1:6789 connection failed
Jun 16 17:26:15 gitega last message repeated 4 times
I would have expected the "umount" to terminate at least after some
generous timeout.
Ceph should probably support something like the "soft,intr" options
of NFS, because if the only supported way of mounting is one where
a client is more or less stuck-until-reboot when the service fails,
many potential test-configurations involving Ceph are way too dangerous
to try...
Regards,
Peter Niemayer
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
