Created attachment 330794 [details] Screenshot of shutdown process, hung at trying to unmount a remote filesystem Bug 239347 relates to a problem with shutdown while NFS filesystems are in use. However, this problem affects non-NFS remote filesystems as well, such as SSHFS filesystems. The system won't finish shutting down if it finds a remote filesystem that doesn't unmount cleanly, and my only option for rebooting is to force the power off. Forcing the system off thus risks corrupting local filesystems that haven't yet unmounted cleanly. I've lost my local filesystem superblock and some user data multiple times because of this. If a complete solution isn't available, perhaps a workaround: the local filesystems could be unmounted BEFORE the remote/network filesystems -- so that if the system hangs on unmounting remote filesystems, at least no local data is put at risk. It could be something as simple as network trouble that causes a remote filesystem to hang. I don't want to put my local filesystems at risk because of network problems (or remote server problems) that I don't have control over. Example screenshot attached.
Created attachment 330796 [details] emerge --info
*** This bug has been marked as a duplicate of bug 239347 ***
(In reply to comment #0) > If a complete solution isn't available, perhaps a workaround: the local > filesystems could be unmounted BEFORE the remote/network filesystems -- so > that if the system hangs on unmounting remote filesystems, at least no local > data is put at risk. There is a problem with this "workaround" though. Suppose /home is a local filesystem but /home/foo is a network filesystem. You can't unmount /home without unmounting /home/foo first.
(In reply to comment #3) > (In reply to comment #0) > > If a complete solution isn't available, perhaps a workaround: the local > > filesystems could be unmounted BEFORE the remote/network filesystems -- so > > that if the system hangs on unmounting remote filesystems, at least no local > > data is put at risk. > > There is a problem with this "workaround" though. Suppose /home is a local > filesystem but /home/foo is a network filesystem. You can't unmount /home > without unmounting /home/foo first. Good point. Feel free to close this bug now, since the only other option I know of is "umount -lfr /mnt/remote" which Bug 239347 already mentions.
Ok, I am closing this per your request.