When a file or directory is set with "set Group ID", the convention is that all new files/directories created under that get the group of the file/directory and not the one of the creator.

Gluster doesn't follow this however, so any file or directory created within a setgid directory will have incorrect permissions.


To recreate:

(on gluster client, as root):


mkdir foo
chown nobody:nobody foo
chmod 2775 foo

cd foo

touch blah

blah will have group ownership of "users", but should have it of "nobody" as the setgid bit is active.