copperhound

I'm guessing the 'default_permission' flag both enables the basic permission checking on the command line, but simultaneously breaks the extended acl checks in samba?

Because of This post I decided to try downgrading to 6.9.2 and the ACLs worked. I'm not sure what these mount options mean, but maybe they would explain why it works in 6.9.2 but not 6.10.3: 6.9.2 ACLs work: root@nas:~# mount | grep /mnt/user shfs on /mnt/user0 type fuse.shfs (rw,nosuid,nodev,noatime,allow_other) shfs on /mnt/user type fuse.shfs (rw,nosuid,nodev,noatime,allow_other) 6.10.3 ACLs do not work: root@nas:~# mount | grep /mnt/user shfs on /mnt/user0 type fuse.shfs (rw,nosuid,nodev,noatime,user_id=0,group_id=0,default_permissions,allow_other) shfs on /mnt/user type fuse.shfs (rw,nosuid,nodev,noatime,user_id=0,group_id=0,default_permissions,allow_other) Should we get this post moved to bug reports? E: I should not that sudo -u test was not working for testing permissions in 6.9.2, but the ACL worked correctly in my samba shares.

I don't know if I'm doing something wrong here or if it is just an unsupported feature or bug, but unraid seems to be ignoring all extended ACLs set under /mnt/user. For example I have a file test.txt with the following ACL # getfacl /mnt/user/test/test.txt getfacl: Removing leading '/' from absolute path names # file: mnt/user/test/test.txt # owner: root # group: root user::rw- user:test:rw- group::rw- mask::rw- other::--- But I am unable to access it as "test" user: # sudo -u test cat /mnt/user/test/test.txt cat: /mnt/user/test/test.txt: Permission denied The ACL does work when accessing a specific disk: # sudo -u test cat /mnt/disk5/test/test.txt You can read the test file! Any Ideas how I can get this working, or even if it is supposed to work? I am running version 6.10.3