Hello All,
Found an anomaly with how a quota is being applied on a vFiler and it feels like I must be missing something obvious.
We have a vFiler that serves up a couple of hundred folders for researchers. This is on 7.3.5 so the aggregate is limited to 16TB. We've set a 500GB quota per folder (qtree), strictly to hopefully keep any one researcher from tanking the filer.
Here's the /etc/quotas file:
#Auto-generated by setup Fri Dec 18 11:16:33 PST 2009 * tree@/vol/cs_researcher 500G - 450G - - /vol/cs_researcher/Rue_R tree 13G - 10G - - /vol/cs_researcher/tosh_M tree 1024G - 950G - -
If I read this correctly, all qtrees are limited to 500G with two exceptions, me (testing) and one researcher that we allowed to go to a TB.
But if I look at the volume I have one folder with 6TB in it. But if I run a "quota report" on that qtree, it says they're using 437GB: cs@tungsten-a> quota report /vol/cs_researcher/Bradley_P K-Bytes Files Type ID Volume Tree Used Limit Used Limit Quota Specifier ----- -------- -------- -------- --------- --------- ------- ------- --------------- tree 16 cs_researcher dley_P 458297068 524288000 3261880 - /vol/cs_researcher/dley_P
It's worth noting that a Windows reporting tool (TreeSize) shows the folder has 350K folders and 11.3M files but the above shows 3.2M files. In either case, will that overload the system's ability to track usage? And why would the two tools show two numbers?
Also, while the well-behaved folders are primarily touched via NTFS/CIFS and show AD owners, the tricky folder is mostly NFS and shows as owned by root. But while we often hit quota situations on our home drive filer (user based quotas) where garbled ownership mixes up quotas, in this case (qtrees) it shouldn't make any difference?
Am I missing something?
Hope to hear from you,
Randy