Bug 466352 - Mount command does not display acls on initially built filesystems
Mount command does not display acls on initially built filesystems
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: util-linux-ng (Show other bugs)
9
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Karel Zak
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-09 16:31 EDT by Nick Gray
Modified: 2009-06-01 04:52 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-06-01 04:52:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nick Gray 2008-10-09 16:31:57 EDT
Description of problem:

A filesystem that is created during the install process, has acl support. This does not show in the mount command. in order to get acl support after the original filesystems have been built, you must use the "acl" option in either the fstab or with the mount command.


Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Create an ext3 filesystem during the build called test1
2. log in
3. cd to test1, touch testfile.
4. setfacl -m u:root:r testfile (note that this works)
5. type mount and notice that the test1 filesystem does not show any options
6. umount test1, mkfs.ext3 on the filesystem that test1 was mounted on and remount
7. perform steps 3-5 again, note that this time you get an error during the setfacl, note that mount shows no options.
8. umount /test1 again and mount with the -o acl option. This time you will be able to see the option
in the mount command. 
  
Actual results:

mount does not show acl option if it is being used

Expected results:

on systems built by the install, 

Additional info:
Comment 1 petrosyan 2008-10-09 17:38:34 EDT
What version of Fedora and util-linux-ng are you using?

'cat /etc/redhat-release'
and
'rpm -q util-linux-ng'
Comment 2 Karel Zak 2008-10-09 18:32:24 EDT
All default (built-in) kernel mount options are invisible for mount(8). mount(8) output is based on the mount command options and fstab. If you need precise information you have to read /proc/mounts.

man mount (BUGS section):

  It  is  possible  that  files  /etc/mtab and /proc/mounts don’t match. The
  first file is based only on the mount command options, but the content of the
  second file also depends on the kernel and others settings (e.g.  remote NFS
  server. In particular case the mount command may reports unreliable
  information about a NFS mount point and the  /proc/mounts file usually
  contains more reliable information.)

 .. it's also true for some non-NFS options of course.
Comment 3 Nick Gray 2008-10-09 20:55:31 EDT
Thanks for the info on /proc/mount. My concern is that there is nothing (in the fstab) telling the system to mount the / filesystem with the "rw,relatime,errors=continue,user_xattr,acl,data=ordered" options, which is what I see in /proc/mounts. for the filesystem that the initial install created

And when I do the test previously mentioned, a mkfs.ext3 on the test 1 filesystem and remount it with a "mount -a" it comes up with

 "rw,relatime,errors=continue,data=ordered"

Which is missing 

user_xattr & acl

I am pretty sure that is what is indicated by "defaults" but how did the other filesystem have these options?  I didn't change anything in the fstab.

Fedora release 9 (Sulphur) and util-linux-ng-2.13.1-8.3.fc9.x86_64
Comment 4 Karel Zak 2009-06-01 04:52:34 EDT
Try:
  tune2fs -l <device> | grep "Default mount options"

you can modify the default mount options by "tune2fs -o" (see man page), but recommended is to define mount options in fstab or course.

Note You need to log in before you can comment on or make changes to this bug.