Hello, on our cluster where we have Scientific Linux 5.4 (64-bit, kernel 2.6.18-164.11.1) and Lustre 1.8.2 we are experiencing problem with setting of default ACLs.
According to rules, newly created files and directories in the directory with a default ACLs set, get permissions of the parent directory, thus ignoring the value of umask. As we have checked this is really the case on Linux with ext3, but we can not make this working in Lustre. Here is an example. On ACL enabled linux (Ubuntu Lucid,32-bit, kernel 2.6.32-21-generic-pae): > mkdir noalc > mkdir acl > setfacl -d --set u::rwx,g::rx,g:atlas:rwx acl > getfacl -c acl default:user::rwx default:group::r-x default:group:atlas:rwx default:mask::rwx > umask 0777 > mkdir noacl/dir > ls -l noacl d--------- 2 root root .... dir > mkdir acl/dir > getfacl -a acl/dir user::rwx group::r-x group:atlas:rwx mask::rwx So, here everything is okay. But, on Lustre the last command above looks as follows > getfacl --access --omit-header acl/dir user::--- group::r-x #effective:--- group:atlas:rwx #effective:--- mask::--- So, the value of umask is not ignored. Does somebody else experience the same problem? What could be wrong in our lustre setup? As usually ACL on MDS is enabled by mount -o acl.. The same problem is in lustre 1.6.6. Thank you very much for any help! Best wishes, Gizo Nanava _______________________________________________ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss