I am seeing some strange behavior with both ACL inheritance and chacl
operation. Does anyone else see this or is my build faulty?
I started with a freshly formatted xfs partition on /mnt/xfs_part.
I set the access, default and mask ACLs for this parition as follows:
[root@jtsdell /mnt]# mount /mnt/xfs_part/
[root@jtsdell /mnt]# chacl -l xfs_part/
xfs_part/ []
[root@jtsdell /mnt]# chacl -b u::rwx,g::rwx,o::rwx,m::rwx u::rwx,g::rwx,o::rwx
xfs_part
[root@jtsdell /mnt]# chacl -l xfs_part/
xfs_part/ [u::rwx,g::rwx,o::rwx,m::rwx/u::rwx,g::rwx,o::rwx]
So far... so good!
[root@jtsdell /mnt]# exit
exit
[jt@jtsdell xfs_backup]$ cd ..
[jt@jtsdell /mnt]$ cd xfs_part
[jt@jtsdell xfs_part]$ ls
[jt@jtsdell xfs_part]$ touch jt.txt
[jt@jtsdell xfs_part]$ chacl -l jt.txt
jt.txt [u::rw-,g::rw-,o::r--]
Not good... Shouldn't this get the default ACLs u::rwx,g::rwx,o::rwx ?
[jt@jtsdell xfs_part]$ su
Password:
[root@jtsdell xfs_part]# touch root.txt
[root@jtsdell xfs_part]# chacl -l root.txt
root.txt [u::rw-,g::rw-,o::r--]
Hmm... root has the same problem!
[root@jtsdell xfs_part]# chacl -B root.txt
chacl: error removing access acl on "root.txt": Invalid argument
chacl: error removing default acl on "root.txt": Invalid argument
[root@jtsdell
xfs_part]# chacl -D root.txt
chacl: error removing default acl on "root.txt": Invalid argument
Shouldn't 'chacl' be removing my ACLs here?
I can go back and manually set the ACLs without problem, but they don't seem to
propogate down correctly and chacl removal seems flawed. I have downloaded a
fresh copy of the CVS tree and will try with an updated kernel and cmd tools
later today. I noticed that chacl hasn't been changed in a while. Maybe it
bears looking into.... (I'll take a peek while the system is hoisting itself by
it's own petard!)
--
John M. Trostel
Linux OS Engineer
Connex
jtrostel@xxxxxxxxxx
|