Red Hat Bugzilla – Bug 122272
(FAT)Unmounting then remounting doesnt update permissions
Last modified: 2015-01-04 17:05:36 EST
Description of problem:
I was attempting to mount a vfat drive onto /media/storage and edited
the fstab the first time with the default options. Then i realized
that only root had rw priveleges and i edited the fstab to give those
privs to everyone in a group (501). However after unmounting the
mountpoint and the remounting from the fstab via "mount -a" the mount
point remounted and reported that the permissions were changed (when
you type mount to see the mounts) but the actual mountpoint was still
like the original mount.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. edit fstab and add line to mount a vfat drive with defaults:
/dev/hda2 /media/storage vfat default 0 0
2. mount the fstab (mount -a) and check the privs (mount)
4. unmount the mountpoint via unmount (be sure to close anything using it)
5. edit the fstab entry to be:
/dev/hda2 /media/storage vfat
gid=501,umask=002,noexec,user,nosuid 0 0
6. remount the drive (mount -a) and check the permissions (mount)
no permission change
change permissions to 775 for users in group 501
you dont have to use groups or the names i used to see the
effects/error i just like to promote good security :)
Ill be happy to reply to clarification requests this is an odd bug for me.
oops there is no step 3 ignore the skip :)
When you umount are you the final unmounter (eg is it also mounted by
nautilus or similar) - what does df say at that point
ocassionally the device reports that it is busy and i am forced to do
a lazy unmount. Regardless of the type of unmount though df reports
the drive unmounted and mounted when it should be. Is there a way to
see/clear anything with locks on the drive? i dont think nautilus
gives the locks up very reliably.
Nautilus should do so if the window is closed. Fam sometimes holds on
to them for a bit longer, which is a problem being investigated
Are you unable to reproduce? Mine works without fail. If you dont get
the same results id like to post and explicit walkthrough so you can
see the issue. Lie i said earlier, it works if you reboot so i dont
really care if it is fixed for functionality sake but i wasted quite
some time thinking i was going crazy. :)
is this still a problem with the latest updates ?
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.