Finally decided to migrate my company's TrueNas server from Core to Scale (Angelfish). Looked like it went swimmingly. Came in today to acl problems that didn't manifest themselves in Core with the same basic setup.
What's going on is a file written to a file share through SMB, the file is no longer accessible through NFS. This doesn't occur the other way around. Tracked it down to file system acl's being changed from the assigned user and owner in the file system to the ad acl of the user/group writing the file under the smb share which makes it untouchable under NFS. Under core, if IRC, all of the underlying AD acl's were not applied to the filesystem owner and user. Is there a way to setup the prior behavior under Scale? I know NSFV4 acls have been implemented and I'm sure this is why, but is there a way to let it work the way it did in Core?
What's going on is a file written to a file share through SMB, the file is no longer accessible through NFS. This doesn't occur the other way around. Tracked it down to file system acl's being changed from the assigned user and owner in the file system to the ad acl of the user/group writing the file under the smb share which makes it untouchable under NFS. Under core, if IRC, all of the underlying AD acl's were not applied to the filesystem owner and user. Is there a way to setup the prior behavior under Scale? I know NSFV4 acls have been implemented and I'm sure this is why, but is there a way to let it work the way it did in Core?
