Red Hat Bugzilla – Bug 126441
nautilus "unmount volume" fails when manually mount doesn't match /etc/fstab
Last modified: 2013-03-05 22:40:53 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
Description of problem:
Manually mounting, for example, a USB stick, with arguments that don't
match an entry in /etc/fstab but using the same mount point, fails.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. mount a USB stick manually as a different device (for example,
/dev/sdb1) that doesn't match the entry in /etc/fstab for that mount
point (/dev/sda, for instance)
2. Unmount the volume using nautilus
3. Watch error message about this volume not being mounted, as
nautilus reads /etc/fstab instead of /etc/mtab for the system's
Actual Results: Should have unmounted the volume.
Expected Results: Error message.
An example to clarify:
Entry in /etc/fstab
/dev/sda /mnt/stick vfat noauto,user 0 0
Manual mount command
mount -t vfat /dev/sdb1 /mnt/stick
Nautilus then gets confused, thinking that the stick is at /dev/sda,
not /dev/sdb1, when it tries to unmount volume per user request.
Nautilus just uses the "umount" command to unmount. All error messages
are just extracted from umount output.
Reread the bugzilla entry. This is not about the error messages from
umount. It's about the fact that nautilus isn't checking where the
device is truly mounted, reading instead /etc/fstab not /etc/mtab.
Reread the code. Nautilus calls "umount /mnt/stick", it doesn't read
fstab, nor mtab for this.
Then something even more problematic is afoot here. What you're
telling me is that mount/umount is broken.
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.