+++ This bug was initially created as a clone of Bug #1246275 +++ Description of problem: When enabling support for POSIX ACLs on a FUSE mount with the "-o acl" mount option, permission checks only use the first 32 groups of a user. If permissions of a directory/file are permitted by groups further in the group-list, the permissions are not applied. The group-list of the user is truncated to the fist 32 groups. Version-Release number of selected component (if applicable): mainline How reproducible: 100% Steps to Reproduce: 1. mount a volume with "-o acl" 2. create a lot of groups (33 or more) 3. create a user that belongs to a lot of groups 4. create a directory on the volume 5. add a POSIX ACL to the new directory, allow writes for the directory to the last group the user belongs to (setfacl -m g:123456:rwx /path/new/dir) 6. create a new file in the director as the user Actual results: "Permission denied" Expected results: The user should be allowed to create the file, the user is member of the group with write access. Additional info: If the number of groups the user belongs to is higher than ~93, the volume option server.manage-gids needs to be enabled too.
REVIEW: http://review.gluster.org/11875 (fuse: add "resolve-gids" mount option to overcome 32-groups limit) posted (#1) for review on release-3.7 by Niels de Vos (ndevos)
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-glusterfs-3.7.5, please open a new bug report. glusterfs-glusterfs-3.7.5 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://www.gluster.org/pipermail/gluster-users/2015-October/023968.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.5, please open a new bug report. glusterfs-3.7.5 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://www.gluster.org/pipermail/gluster-users/2015-October/023968.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user