I need to migrate a bunch of users home directories onto our FAS2240
Currently they are all folders within a hidden share off our main fileserver and each folder has permissions set so only that the user can only access their own folder. Each user has a 10GB quota.
I have been looking at using the cifs_homedir.cfg and specifying ntname for the naming convention but I cannot work out how to apply a quota that will apply to each user.
Could somebody point me in the correct direction ?
here is my working example. Replace *DOMAIN_NAME* with your Windows Domain Name:
create qtree /vol/userhome/*DOMAIN_NAME*
/etc/quotas is attached.
Default Quota is set to 1GB. Exceptions needs to be configured afterwards.
Set home dirs hidden:
FILER> options cifs.ho
options cifs.home_dir_namestyle hidden
options cifs.home_dirs_public_for_admin on
Admin has to set change permission for user1 to /vol/userhome/*DOMAIN_NAME*/user1.
Note: only user1 can get access to \\filer\user1$. Users who already mapped a share from \\filer are not able to map share \\filer\user1$ even if they use user1's credencials. This is a great feature of NetApp home_dir implementation.
my report looks like this.
Type ID Volume Tree Used Limit Used Limit Quota Specifier
----- -------- -------- -------- --------- --------- ------- ------- ---------------
user * vol_tt_homes - 0 10485760 0 - *
user \ukawood vol_tt_homes - 0 5120000 0 - ukawood
user \Adminis vol_tt_homes - 7044272 - 9 -
which looks to me like the files are counting towards the Administrators quota rather than mine since the 2 files add up to just over 7GB. NT permissions are set for me as owner and read/write access.
ok I figured it out. My user account is a member of a group that is itself a member of the BUILTIN\Administrators group. It seems that this means any files I write to the filer has the owner set to the BUILTIN\Administrator group so quotas are not applied.
Is there any way I can stop this behavior ?
Not sure I would call it standard windows behavior. Windows usually sets ownership to be the the User rather than a group the user happens to be in. It looks to me like the NetApp is purposefully setting the owner to be the id of the Administrators group rather than the id of the user writing the file.