Hide Forgot
We use only fuse clients (we do export fuse-mounted volume via non-glusterfs nfs for the macs, please don't ask why) Suppose we have ha user: user with group group (and additional groups group2) If I create a directory: test (with 0750) and user:group, everything is as expected. If I now have: directory (0750, someuser:group2) directory/user1 (0700, someuser:group) directory/user2 (0700, user:group2) directory/user3 (0700, root:root) then only "user3" is listed, when "user" does an ls In contrast to the bug mentioned above, we have this problem with secondary groups if "directory" is owned by another group. In our case: all users are in "group2" (a secondary group), their directories, user1,user2,... are all owned by username:primarygroup with 0700 only root can see the directories. The same test case worked fine for me, opening a bug in case we can identify a variation of this procedure resulting in the bug.
I believe I'm seeing the same problem in a different way using 3.2.2 and in 3.1.1. Specifically, one creates a directory owned by user A and belonging to group G. With attributes set to 770, user A can enter, read and write this directory. However, user B who is a member of group G (and G is not his primary group) is not allowed to enter the directory. Please, please, please fix this problem.
Hi Jeff, we suspect it to be an issue with fuse's auxiliary group problem, which got fixed in some of the recent versions of gluster releases. please try 3.3.0+ version and see if its fixed now. We are not able to reproduce the issue any more with the current versions, and will be closing the bug as WORKSFORME, please re-open if it still doesn't work for you.