When using the ACL Editor in Truenas Scale 24.10, and using the “Apply permissions recursively” option, it doesn’t seem to be setting my custom groupIDs throughout the sub-folders.
It seems to have reset all of the default and root permissions, and the root and default ACLs permissions I set do show under setfacl.
However, none of the new groups I added get set.
It should be doing this. Are these subdirectories or child datasets (they are different things).
At this moment, they are all just folders - no child datasets.
Do i need to strip all permissions first?
getfacl is often the wrong tool to use (unless you’re using POSIX1E ACL type).
Seeing the same. They are applied to dataset directory, but not to files or sub directories.
Edit: When using POSIX ACL, didn’t try with NFS4 ACL.
I’ve ended up calling setfacl recursively from within shell.
yep, that’s what I’ve had to do since the OP.
kind of an setfacl expert now.
Can you describe the problem more clearly? Maybe show what is being submitted to backend midclt call core.get_jobs | jq. If there’s a bug bug, it won’t get fixed by “me too” posts 
Us plebs are not versatile with such technology know-how.
But we’re sure someone such as yourself has the means to follow our directions to attempt to re-produce it with your vast knowledge of the system.
Works for me, hence the question. No need for the snark.
If I were to hazard a guess, you’re probably not creating default entries. POSIX ACLs actually have two lists. The ACCESS list that applies to the current file / directory and the DEFAULT list that applies to new files / directories. Basically your DEFAULT ACL defines how inheritance will behave. It’s not an intuitive a design as the NTFS / NFSv4 module, but this is how the POSIX1E draft specifications were written about 25 years ago.
When you perform a recursive ACL operation on a POSIX ACL dataset we take the DEFAULT entries and apply them recursively (as if the ACL on files within the dataset inherited them during normal file creation operations).
So, only the permissions with flag “Is Default” are applied recursively then? Thanks for clarifying this out, it’s really not intuitive at all.
Perhaps in future there could be an update to info to [ ] Apply permissions recursively stating this - I bet it’d avoid a lot of questions.
Just had the same issue.
Even looked at the default box but with no tooltip re what it does it’s relevance was not clear 
