11.2 U2 changes how SMB share permissions work
I no longer have write access to my smb shares. I can create and read files, but not modify or delete. Even if I do chmod 777 on the files or folders, I'm still unable to delete them from windows explorer. Switching to the user that has ownership of the files in the terminal, permissions work as expected so this is purely via smb.
If I re-set up the shares with "Apply Default Permissions" checked, then it works correctly. However, a + is added to the folder, and a .windows folder is created inside of it even though the folders are set up with Unix Permissions. When I go to check the permissions on the dataset, it is now set to Windows permissions.
I have always used unix permissions, because I access the smb shares from a combination of Windows and Linux VMs, and I like to be able to see and modify what the permissions are directly from the terminal. This is really useful for me especially remotely over vpn via ssh.
Is this new functionality intentional? It essentially makes unix permissions + smb shares unusable. I understand that I could just use windows permissions, but this feels clumsy for me given I've only got a few users, and my permissions requirements aren't very complicated. When I looked into using windows permissions previously, it seemed that permissions could only be modified within windows explorer. (Although I'm aware there are sets of commands other than chmod and chown that I never learned to use that deal with the more complex permission set.)
I have tested this on two different FreeNAS systems that I upgraded to 11.2 U2 today, and they behave identically.
Reverting back to 11.2 release (I skipped 11.2 U1) fixes the issue with no other changes needed. Unix permissions and smb shares work again.
#1 Updated by Mike Gittelman over 1 year ago
After doing some more research, it seems the recommended way of sharing via SMB is to use Windows permissions. In essence I've been doing it wrong, even though it's been working well? If so, it does appear that something changed in the latest release which broke my set up, but if the recommendation is to comply with the standard way of doing it, I can understand that.
#5 Updated by Mike Gittelman over 1 year ago
In case it's helpful, forum post is here: https://forums.freenas.org/index.php?threads/11-2-u2-changes-how-smb-unix-share-permissions-work.73943/#post-512928
Removing zfsacl seems to correct the behavior. Replacing zfsacl with ixnas also seems to correct.
#10 Updated by Dru Lavigne over 1 year ago
- Status changed from Ready for Testing to Done
- Target version changed from 11.3-BETA1 to Master - FreeNAS Nightlies
- Reason for Blocked deleted (
Need additional information from Author)
- Needs QA changed from Yes to No
- Needs Doc changed from Yes to No
- Needs Merging changed from Yes to No