Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 256649

Summary: sys-fs/sshfs-fuse + sys-apps/baselayout-1.12.11.1 - netmount fails to unmount sshfs mounted filesystem
Product: Gentoo Linux Reporter: Richard Scott <gentoo.bugs>
Component: [OLD] baselayoutAssignee: Stefan Schweizer (RETIRED) <genstef>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kernel-misc
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Richard Scott 2009-01-28 16:07:48 UTC
Hi,

I have a server with sys-apps/baselayout-1.12.11.1 and I have been having problems rebooting when I have something mounted via sshfs.

For example, if you have an entry in your /etc/fstab as follows:

sshfs#root@server:/root /root fuse _netdev,defaults 0 0

The /root mount point is mounted at boot time via netmount :-)

However, netmount fails to unmount this mountpoint when you stop the service i.e. rebooting or poweroff etc.

When shutting down in this way it causes the computer to hang and wait for ever as the sshfs mount point hasn't been unmounted.

I don't think this is the right wat to fix it but I've found that you need to change NET_FS_LIST line in /sbin/functions.sh (aka /etc/init.d/functions.sh) to include fuse.sshfs as follows:

NET_FS_LIST="afs cifs coda davfs fuse gfs ncpfs nfs nfs4 ocfs2 shfs smbfs fuse.sshfs"

I think this is because the "netmount start" uses /etc/fstab as its source of filesystems to mount and the "netmount stop" uses information from /proc/mounts.

The /proc/mounts file lists the filesystem type as "fuse.sshfs" rather than just fuse so it doesn't get detected to be unmounted via netmount as its not in its list of ones to look for.

I hope this can be worked into an updated script.

Cheers,

Rich.


Reproducible: Always
Comment 1 Peter Volkov (RETIRED) gentoo-dev 2009-08-26 17:27:13 UTC
Thank you Richard for investigation. We already have this bug filled so I put patch for this issue there and assign that bug on base-system.

*** This bug has been marked as a duplicate of bug 248878 ***