Bug 761788 (GLUSTER-56)

Summary: group guid does not work
Product: [Community] GlusterFS Reporter: Caleb Tennis <caleb.tennis>
Component: posixAssignee: Vikas Gorur <vikas>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 2.0.1CC: gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Caleb Tennis 2009-06-24 21:41:47 UTC 
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.
Comment 1 Caleb Tennis 2009-06-25 06:36:18 UTC 

*** This bug has been marked as a duplicate of bug 72 ***