[Bug 243373] Re: FUSE Filesystem type mismatch between fstab & mtab prevents umount
Thomas Hotz
243373 at bugs.launchpad.net
Sat Apr 27 16:13:09 UTC 2013
Confirming this bug because it happens to multiple users.
** Changed in: fuse (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to fuse in Ubuntu.
https://bugs.launchpad.net/bugs/243373
Title:
FUSE Filesystem type mismatch between fstab & mtab prevents umount
Status in “fuse” package in Ubuntu:
Confirmed
Bug description:
FUSE filesystems in /etc/fstab, i.e. fstab entries whose fstype is
"fuse," show a different filesystem type in /etc/mtab, which includes
exactly what kind of fuse filesystem it is, for example "fuse.sshfs"
for an sshfs mount. As a result of this mismatch, the filesystem's
owner may not unmount the filesystem using the umount command, but
must either use sudo, or else use fusermount -u.
In Gutsy 7.10, /etc/mtab used the same format that /etc/fstab still
uses. In Hardy 8.04, the mtab format has changed, while the fstab
format has remained the same, causing the fstype disagreement.
Attempting to modify the fstab to match the format shown in the mtab
does not work. Either the fstab should be fixed to accept the new
format, or the mtab format should be reverted.
#example fstab entry for sshfs
sshfs#rct2c: /mnt/sshfs/rct2c fuse rw,uid=ryan 0 0
# corresponding old (Gutsy) mtab entry
sshfs#rct2c: /mnt/sshfs/rct2c fuse rw,user=ryan 0 0
# corresponding new (Hardy) mtab entry
rct2c: /mnt/sshfs/rct2c fuse.sshfs rw,user=ryan 0 0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/243373/+subscriptions
More information about the foundations-bugs
mailing list