- Joined
- Dec 8, 2017
- Messages
- 442
I no longer have write access to my smb shares. I can create files, but not modify or delete. Even if I do chmod 777 on the files, 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.
Is this new functionality intentional? If I re-set up the shares using all windows permissions, does this break my ability to set them via terminal? When I looked into this previously, it seemed that if I use Windows permissions, it meant that permissions had to 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.
Ideas?
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.
Is this new functionality intentional? If I re-set up the shares using all windows permissions, does this break my ability to set them via terminal? When I looked into this previously, it seemed that if I use Windows permissions, it meant that permissions had to 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.
Ideas?
Last edited: