Ok, this might be a dumb question, but I have recently migrated from Truenas Core, I am setting up some new pools and i found I cant manage root dataset permissions in the gui, not even sure how it selected posix permissions, is there a reson that posix is prefered for for root permissions? Just need to understand it compared to my imported pools that use ACL and have them inherited to all datasets within that pool.
Thanks
In my understanding the root dataset should not contain any files or folders. All files or folders should live in child datasets of the root datasets. As such, the root dataset is just an empty folder, setting a ACL there doesn’t make much sense. Not being able to change permissions on the root dataset also means that you can’t mess up the permissions, making it one less potential source of problems during troubleshooting.
I think it was different in older truenas versions? I’ve seen some setups that only used a single dataset without any child datasets, there it does make sense to set acl type.
Thanks bacon, kinda understand why root datasets should be data free, not so clear cut on why we cant change default permissions on root dataset, this makes it easy for all child datasets able to inherit specific permissions unless otherwise specified.
Everything below the root dataset’s path (/mnt/poolname) requires that “other” has read and exec permissions (755). If not, you can and will break access for child datasets, since without x, a non-root user will be unable to traverse the path or create directories below.
Thanks, that makse sense, having a play around with hit as well, i get it now 
