Quota Report doesn’t match Quota Entry

[rancid elbow]

Evening all,

Having a strange issue recently that I’m not sure relates to a recent upgrade to 9.15.1RC2.

If I add a default quota to all users, say 2gb and a user uses all that quota, i then add an explicit quota for 4gb for that user , but the Get-NcQuotaReport powershell cmdlet still shows they have 2gb. Is there a delayed update to the QuotaReport?

I’m pretty sure when we were on 9.12 the quota report updated pretty quickly as we pull the results into a database every hour for service desk usage.

Cheers.

[rancid elbow]

For example. If i do a Get-NcQuota on the user via powershell i get this

But if i look at the quota report, even after a resize operation and a day later it still shows the DiskLimit at 2gb which is the default.

[rancid elbow]

Quota Report doesn’t match Quota Entry

[spice charm]

did you do the quota resize?

[rancid elbow]

Yes sir

We actually have this automated. Our service desk staff use a webform to increase peoples home directory quotas and as part of that it adds or updates their explicit quota and then does a resize. I even did a manual resize for good measure

[spice charm]

hm. strange

[rancid elbow]

Very, pretty sure this worked fine up until we upgraded to 9.15

[spice charm]

btw. you censored the NT domain name but forgot to censor the DNS domain 😉

[rancid elbow]

god dammit!

Even the ontap webui still thinks they have 2gb

[rancid elbow]

So in desperation i switched off the quota on the volume and then switched it back on. Problem solved

I assume creating an explicity quota requires this as its a new quota entry and needs to re-read and loaded.

[spice charm]

yeah, maybe. I thought the resize handles all these edge cases by now but it seems there are still cases where "off+on" is the only solution

[rancid elbow]

Don’t we just love NetApp and its fragmented codebase.