Issues with SMB and inheritance

[eexodus]

FreeNAS 11.1-U6 and Windows Server 2016

user1: a user who owns the file share
file-admins: a group my domain admin account is a member of
share-group: a group who uses the file share
user2: a member of share-group who needs their own private folder

I have a SMB share setup like:
"\\10.0.2.1\share" (root) owned by user1; permissions:

• user1 full
• share-group modify
  
• file-admins full

Inside the share I have a shared group folder:
"\\10.0.2.1\share\shared" owned by user1:

• user1 full (inherited from \\10.0.2.1\share)
  
• admin-group full (inherited from \\10.0.2.1\share)
• share-group modify (inherited from \\10.0.2.1\share)

Files and folders created in "shared" end up with (created by user2):
"\\10.0.2.1\share\shared\test.txt" owned by creator user2

• user2 modify (inherited from Parent Object)
• file-admins full (inherited from Parent Object)
  
• share-group modify (inherited from Parent Object)
  
• user1 goes missing!! even though the Parent Object ("shared") has user1 as full permissions and "shared" is set to inherit

I also have multiple private user folders I need to remove share-group modify from:
"\\10.0.2.1\share\user2" owned by user1:

• user1 full (NOT inherited; inheritance turned off then user1 re-added)
  
• user2 modify (NOT inherited; inheritance turned off then user2 re-added)
• file-admins full (NOT inherited; inheritance turned off then file-admins re-added)

Files and folder created in this user2 private folder named "user2" end up like:
"\\10.0.2.1\share\user2\test.txt" user2 owner

• user2 full (inherited from Parent Object) (I can't get CREATOR OWNER to work either preferably the user2 would just have modify even though they are the test.txt file creator)
• file-admins full (inherited from \\10.0.2.1\share\user2)
• user1 is again missing despite being a full permissions user in the parent object!

 

[anodos]

Try setting the auxiliary parameter

Code:

nfs4:aclmode=simple

to your share.

 

[eexodus]

Try setting the auxiliary parameter

Code:

nfs4:aclmode=simple

to your share.

Thank you! That solved it I think. Just curious why a smb conf referencing nfs4 would be the solution though? Regardless I am happy it is working as expected now. The only issue I continue to have is CREATOR OWNER is not being handled like I think it should, but that may be my lack of familiarity with it. When the parent folder has CREATOR OWNER set to modify child objects created in it still grant full permissions to whichever user created it.

 

[eexodus]

The only issue I continue to have is CREATOR OWNER is not being handled like I think it should, but that may be my lack of familiarity with it.

Looks like it was my lack of familiarity. I forgot to set the parent folder's ownership to the user in question.