Hello,
the ALC permissions on my old TrueNAS Core datasets seem to be either completely wrong or they no longer work with Scale.
For this reason I will set up datasets and ALC from zero and then transfer the data without snapshots.
I’m just unsure whether it makes sense to leave root in the datasets for “owner” and “owner grop”?
If not, what would be best practice here?
Otherwise, I’m planning a group with administrative rights and one with read-only rights. This should make sense, right?
Can you provide more information about this or a system debug?
Unfortunately no more than the information from the other thread.
I have now completely reset everything and started from scratch on the VM.
It’s not a big deal for me to lose the history in the home lab.
The only important thing for me now is to do everything correctly when restarting.
Hence the question of best practice regarding root in ALC.
root is fine for both. That will change once files are created (new files are owned by the user creating them). If dataset is being accessed by processes in an app / non-SMB then you’ll want to keep the default owner@, group@, and everyone@ entries since they correspond with UGO permissions presented to applications when they stat() a file. Some poorly-designed applications may think that file permissions are 000 and error-out.
