https://community.netapp.com/t5/ONTAP-Discussions/Problems-activating-UMASK-on-share/m-p/146319#M32484 <P>After migration of data using 7MTT we run into a problem. On the source Netapp we noticed a UMASK of 0777 is used.&nbsp;</P> <P>In C-mode (running ontap 9.3) you can define the UMASK on the share level. Because a share existed on the volume level we adapted the umask "cifs share modify -vserver XXXX -share-name YYYY -file-umask...." to 0777. We did the same on a qtree defined in the same volume.&nbsp;</P> <P>When&nbsp; dropping a file with a windows-user in the volume, the unix security is change correctly. In case we do the same in the qtree, the security is not succesfully adapted....</P> <P>&nbsp;</P> <P>Anuy idea what is wrong here?&nbsp;&nbsp;</P> Wed, 04 Jun 2025 12:54:31 GMT GrumpyOldMen 2025-06-04T12:54:31Z https://community.netapp.com/t5/ONTAP-Discussions/Problems-activating-UMASK-on-share/m-p/146319#M32484 <P>After migration of data using 7MTT we run into a problem. On the source Netapp we noticed a UMASK of 0777 is used.&nbsp;</P> <P>In C-mode (running ontap 9.3) you can define the UMASK on the share level. Because a share existed on the volume level we adapted the umask "cifs share modify -vserver XXXX -share-name YYYY -file-umask...." to 0777. We did the same on a qtree defined in the same volume.&nbsp;</P> <P>When&nbsp; dropping a file with a windows-user in the volume, the unix security is change correctly. In case we do the same in the qtree, the security is not succesfully adapted....</P> <P>&nbsp;</P> <P>Anuy idea what is wrong here?&nbsp;&nbsp;</P> Wed, 04 Jun 2025 12:54:31 GMT https://community.netapp.com/t5/ONTAP-Discussions/Problems-activating-UMASK-on-share/m-p/146319#M32484 GrumpyOldMen 2025-06-04T12:54:31Z