Hi Iban, What you are seeing is what you get if you call mkdir(2) like this from C
mkdir(“dirname”, 0700); or in a python script like this import os os.mkdir(“dirname”, Oo700) Or you could use chmod on the directory like this: chmod 700 dirname All of these modify the ACL mask entry so that it no longer matches the default ACL mask. Notice how everything else in the ACL still matches the default ACL. You can easily set the mask back with chmod g+rwx dirname (assuming that your fileset is configured to allow chmod). Steve Losen Research Computing University of Virginia [email protected]<mailto:[email protected]> 434-924-0640 From: <[email protected]> on behalf of Iban Cabrillo <[email protected]> Reply-To: gpfsug main discussion list <[email protected]> Date: Tuesday, January 18, 2022 at 11:26 AM To: gpfsug-discuss <[email protected]> Subject: [gpfsug-discuss] Filesystem sometimes does not correctly inherit acls Dear Scalers, We are running 5.1.1-0 version. Since a couple of months we have noticed, that the directory permissions are not inherited correctly even if the default acl is set correctly: For example this is the default acl for a directory (mmgetacl -d): #owner:100 #group:101 user::rwxc group::r-x- other::---- mask::rwxc user:user1:rwxc group:group1:rwx- group:group2:rwx- group:group3:rwx- But sometimes when a new dir is creted under this directory i see this: #owner:100 #group:101 user::rwxc group::r-x- #effective: ---- other::---- mask::---c user:user1:rwxc #effective: ---c group:group1:rwx- #effective: ---- group:group2:rwx- #effective: ---- group:group3:rwx- #effective: ---- Any Idea about this behavior ? Regards, I
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
