Truenas Scale System Data set owned by Active Directory User

j.lanham

Explorer
Joined
Aug 25, 2021
Messages
68
When I migrated from Truenas Core to Scale, I didn't realize that we had Owner and Group as Active Directory Account and Group of the System Data Set. It's causing me no end of headaches as I've almost mitigated everything but delete and move to folder access. Anything that seems to change directory attributes. I'm speculating it's related to the System Data set not being owned by root. Is there a lossless way to change the user and group ownership and keep access to the System Data Set?
 

j.lanham

Explorer
Joined
Aug 25, 2021
Messages
68
I am embarrassed to add that I had installed a backup agent on the server and that was when all the real trouble began. I may be fighting multiple problems. Is there an acl consistency check or a way to repush the existing acls that were created during migration? I know there isn't really a consistency check for openzfs, but perhaps a checking tool I can run. I'm really trying hard to not have to rebuild it.

Or could it be smashed acls at the System Data set level? Would there be a way to reapply the acls?

I really should include the symptoms. Whenever I delete a file under a folder (smb AND nfs) the file comes back a few seconds later. I can't delete some folders. And the delete problem only happens on some folders, but once it tries to delete it the folder itself it unable to be deleted. It doesn't give an error, it just doesn't go anywhere. This was happening under a pure SMB share until I deleted the agent. But I'm sure there are some folders in there that I haven't tracked down. Irregardless, weird and wild stuff. It was working for the most part until the *@#&^$^ backup agent got involved.

It really didn't start happening until after the first backup, which was successful, and then I'm sure it started tracking changes. It could also have been locks, since it locked each file while it was backing it up. I'm not sure what kind of damage I did.

And I just thought of something, maybe the scrub ran while the backup was running.
 
Last edited:
Top