When a file is created with samba 3.5.x or 3.6.x, it is created effective read-only: ~ # getfacl Microsoft\ Word-Dokument\ \(neu\).docx # file: Microsoft\040Word-Dokument\040(neu).docx # owner: root # group: 11816 user::rwx user:11582:rwx #effective:r-- group::rwx #effective:r-- mask::r-- other::--- The ACL settings for the parent directory are ok: ~ # getfacl . # file: . # owner: root # group: 11816 user::rwx user:11582:rwx group::rwx mask::rwx other::--- default:user::rwx default:user:11582:rwx default:group::rwx default:mask::rwx default:other::--- The same Samba configuration on the same filesystem (GPFS) running with Samba 3.4.x is working correctly: [share] read only = no inherit acls = yes inherit owner = yes inherit permissions = yes nt acl support = yes
Created attachment 8583 [details] Logfile log level 10 logfile while creating a new file on Windows 7 client
workaround found: we set "inherit acl = no" and it works. There must be a problem when "inherit acl = yes" is set and default ACLs are used(?)