Description of problem: Setting ACL on a FUSE mounted GlusterFS Volume doesn't work (but it does work when NFS mounting Gluster Volume). Steps to Reproduce: 1. Setup a new disk with xfs as the FS format. 2. Create a new volume using this disk for storage 3. mount this new volume using: mount -t glusterfs -o acl 127.0.0.1:/vol /mnt/vol 4. cd into /mnt/vol 5. create a new file: touch acl-test 6. try set ACL: setfacl -m u:gopher:rw acl-test 7. check ACL is set: getfacl acl-test Actual results: No ACL set Expected results: gopher user to be added into ACL list. Using Gluster 3.4 available in the public Gluster Repo: glusterfs-fuse-3.4.0-3.fc18.x86_64 glusterfs-3.4.0-3.fc18.x86_64 glusterfs-api-3.4.0-3.fc18.x86_64 glusterfs-server-3.4.0-3.fc18.x86_64
Possibly related: https://bugzilla.redhat.com/show_bug.cgi?id=989435
(In reply to Christopher R. Hertel from comment #1) > Possibly related: > https://bugzilla.redhat.com/show_bug.cgi?id=989435 yes, I can confirm that by running "gluster volume set <VOL> stat-prefetch disable" ACL's are now working. Thanks for the tip. Rich
GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5. This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "bugs". If there is no response by the end of the month, this bug will get automatically closed.
This now works for me with v3.4.7 without setting stat-prefetch to disable :-)