2012-04-05 01:17 PM
I have just relocated some file shares onto our NetApp and after the fact found that one of the 25 or so shares needs to have a quota enforced. My understanding is that quotas can only be applied at the root of the volume/qtree. I haven't been able to find any different or figure out how to do what I'm trying to do. It looks like my only option is to create a new volume and move the data from the one share that needs quotas into that volume and point the CIFS to the new location. Does that sound about right or does anyone have a trick? Thanks in advance.
Solved! SEE THE SOLUTION
2012-04-05 01:25 PM
True – quotas can be applied at the qtree level (the q in qtree is for ‘quota tree’ from its initial purpose years ago).
So if it’s the only one within the data set that you want to have quota applied, yes it will have to move into a new qtree, possibly by itself.
If you want it linked or joined with the rest of the directory structure you already have (ie: if it would be nice to have it still placed in the same directory structure you already have), then you can take advantage of symlinks. Search “symlink” in the communities for a picture of what they are, can do, and how to implement.
2012-04-05 01:46 PM
No, sorry, can't apply quota to symlink. I meant to add in the symlink talk only if you wanted to maintain the directory structure, ie: if you users didn't want to do away with an existing directory structure. For the quota part you're looking for, quota can only be applied at the qtree level. You could create a symlink in your existing directory structure pointing to the new qtree which would have the quota.
/vol/new_qtree <- your newly created qtree with quota applied
/vol/existing_qtree/dir1/dir2/dir3/symlink => /vol/new_qtree
Does that help? I maybe misunderstand your goal.
2012-04-05 01:52 PM
You're welcome Adam..
You can still keep all the data in the same existing volume if you like. Just need a new qtree within that volume....you could have the 2 different qtree's (one quota'd, one not).
2012-06-01 02:31 AM
You are going to need to include the relevant parts of /etc/quotas. This looks like an error in your quotas file. You can find more information in the manpage or the system documentation.
2012-06-01 05:09 AM
my /etc/quotas is quite simple:
#Auto-generated by setup Mon Mar 5 07:40:50 GMT 2012
* user@/vol/Home_Dir 10485760K - 8912896K 8912896K -
/vol/FileServer/Frosta tree 943718400K - 880803840K 880803840K -
/vol/FileServer/General tree 524288000K - 471859200K 471859200K -
The third entry (qtree called General) and next new entries generate an Error: quota: skipping new definition for /vol/FileServer/General.
Quota status for volumen FileServer are on.