Hi,
I can confirm the exact same issue with a fresh install of 11.2-U6, during which I initialized a brand new dataset (/mnt/tank/).
I ended having no permissions for "everyone@" on this new dataset:
Code:
everyone@:--------------:-------:allow
This actually led to this issue with shares (and days of investigations...): access was possible by the owner or group, but all other permissions were ineffective.
I got plently of those entries in /var/log/samba4/log.smbd:
Code:
[2019/11/22 10:05:41.351965, 0] ../source3/smbd/uid.c:453(change_to_user_internal)
change_to_user_internal: chdir_current_service() failed!
As suggested above, I just applied the proposed workaround:
Code:
# set default permissions
setfacl -m everyone@:rxaRc:d:allow /mnt/tank01/
setfacl -m everyone@:rxaRc:d:allow /mnt/tank01/nas
# propagate to the whole "nas" dataset
winacl -a clone -rv -p /mnt/tank01/nas
And it seems to work perfectly now.
I'm new to Freenas, so maybe I did a mistake that broke the default ACL... but frankly I can't remember touching anything on ACL before facing this issue.
Do you think there could be an actual issue with ACL initialization on newly created datasets, using v11.2-U6 (and U7 possibly)?