> Gah, is umount replaced by something via systemd? I mean.... umount is > still umount, no? > > IOW is this just doing a lazy unmount behind your back? My interpretation is that at the time a service is started, the entire filesystem "namespace" is copied to a secret place, including the mounts. Then, when I issue umount, it is actually unmounted from the main namespace, but from the viewpoint of the filesystem, it's still mounted, precisely in the hidden namespace that got created for the running service. Only when this service quits, its namespace will be destroyed, and with it the filesystem's refcount will drop to 0. At this point, the real "unmount", or rather "close" will happen. Apparently, this is not usually a problem, but for me it is, because at that time, the iSCSI storage device is gone. Gabriel has filed a bug here: [1]. Unfortunately, I have no hope that this will ever be "fixed", because it behaves just the way it was designed :(. At least it has become clear that this has nothing to do with XFS, although subjectively my feeling is that the effects (i.e., data loss) are felt more with XFS than with ext4. [1] https://bugzilla.redhat.com/show_bug.cgi?id=851970 _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
