This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

If you are sharing the parent dataset then it will need to be NFSv4 ACL type as well. As is stated in the alert.

Maybe i am miss understanding the “Apps” dataset preset. If it will always create an NTFs share i need to redo the overarching dataset. However I can reiterate the steps and share 2 more screenshots too.

• I have my main dataset for all applications (/tangycentral).

  • It a unix share.

  • Below that i create datasets for each application.

  • Every time i create a new one from the dataset UI (for use in custom docker compose files) i choose the “apps” preset

  • When creating a dataset from the app installation interface (discover) this dataset gets the unix share permissions

• When i create a new dataset (tangycentral/golinks) i go to datasets > select the apps dataset > create new > apps preset > Save

  • here it auto creates the ntfs share as a subset on my unix share.

  • i get the error message and the general mess around it

I don’t understand the bug report. Is it that you were allowed to do something that generates an alert? You shouldn’t have mismatched ACL types on datasets within a single SMB share.