NFS permissions won't stick to two folders

[John45622]

Hi,
I'm running Scale 23.10.1.1 and have an NFS share containing two folders that just won't "accept" the ACL permissions. I have stripped and re-applied the permissions in this way to the entire Dataset.

However 2 of the folders on the top level (and everything they contain) of the dataset seem to be read only in a strange way. I can create a folder, but can't name it. I can also not write to that folder or do anything else.

Literally every other folder on that Dataset can be fully modified.
I've stripped and re-applied the permission multiple times to the dataset recursively but it's always the same two folders exhibiting this behaviour. I also tried creating a new folder in order to copy the content of the weird folder into that new one but this also leads to an error. I can play the media inside the folder (wav-files) but it won't let be copy them.
Why am I doing wrong?

Thanks!

 

[John45622]

I also tried this after stripping ACLs but no change:

 

[John45622]

Tried some more things incl. switching to POSIX from SMB/NFS ACLs and back, again stripping and re-applying permissions recursively to the entire dataset but no luck.
I can also not delete those two folders in order to copy back an external backup. The only thing I can do it play back the wav files in OSX finder. Nothing else. Can't copy, can't delete, can create a new folder inside those two folders but can't rename it and I can delete it but just the newly created one. Nothing else in that folder.
What is going on here?

 

[anodos]

My guess is that your IDs on the Mac / account used don't match what's on the TrueNAS server. Generally you have a few options with how to manage permissions with NFS:
* Use AD / LDAP to make all users / groups have consistent IDs (on both server and client)
* Use kerberos + NFSv4 and the above (which adds actual security security and may relax the idmapping requirements slightly)
* Use mapall / maproot parameters.

 

[John45622]

Thank you!

Thing is: I have permissions set to allow all at the moment and I am an admin on the client. And ALL files and folder on the dataset have the same permissions and yet two of them I can not change or delete. Every thing is jolly and working fine except for two of the folders (when connecting from the same machine/user) to the server.

I tried setting mapall/maproot but no change.

 

[anodos]

Thank you!

Thing is: I have permissions set to allow all at the moment and I am an admin on the client. And ALL files and folder on the dataset have the same permissions and yet two of them I can not change or delete. Every thing is jolly and working fine except for two of the folders (when connecting from the same machine/user) to the server.

I tried setting mapall/maproot but no change.

Are they directories or dataset mountpoints?

 

[John45622]

It's a Dataset setup as NFS share.

 

[John45622]

(side note)
The only reason I'm using NFS instead of SMB is that browsing folders with many items is lightyears faster via NFS than SMB even though I get about 5-10 times better read/write performance via SMB than via NFS. Not sure why but NFS feels MUCH more snappy oder OSX. Transferring large amounts of files is much faster via SMB but this dataset is 90% for read operations so I switched to NFS.
SMB is a lot easier to manage in terms of permissions so I don't mind SMB per se. But this dataset is accessed by 2 clients anyway so LDAP etc. seems like total overkill at the moment.

But all that set aside I see no reason why 2 of my folders can not be changed while all others including the content can be.