Updating/creating too many quotas in a short time span causes errors and quota to not be applied

[Jascha-N]

The error message reads:

Quota policy rule create operation succeeded, however quota resize failed due to an internal error. To make quotas active for volume "project" in SVM "atreides", disable quotas for the volume and then re-enable them again.

or:

Failed to obtain volume quota state or invalid quota state obtained for volume "project" in SVM "atreides". Fix the issue and retry the operation

The quota will be stuck on a default 10GB until manually reactivated or "resized".

https://community.netapp.com/t5/ONTAP-Discussions/Python-Rest-Api-quota-error/m-p/164921

[hurngchunlee]

This can only be fixed by calling "quota resize"; however, there is no such interface available in the NetApp Rest API. The link above indicates that the fix has been provided in ontap 9.8

two options:

• apply a cron job to run quota resize every hour, or
• upgrade ontap to 9.8 (we are currently running 9.7P14)

@RenedBruin what do you think?

[RenedBruin]

Hi Hong, apply cronjob, Updating has to be done by netapp asistance preferable. remove cornjob when done.

…

On Mon, Jan 3, 2022 at 3:52 PM Hurng-Chun Lee ***@***.***> wrote: This can only be fixed by calling "quota resize"; however, there is no such interface available in the NetApp Rest API. The link above indicates that the fix has been provided in ontap 9.8 two options: - apply a cron job to run quota resize every hour, or - upgrade ontap to 9.8 (we are currently running 9.7P14) @RenedBruin <https://github.com/RenedBruin> what do you think? — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGBVCZZMRCFR2QNT2DXVH43UUGZZFANCNFSM5KVX6DEQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[hurngchunlee]

@Jascha-N I am curious about your test result after I implemented the enforcement of the PATCH call on the quota rule API. I have a feeling that if it a known issue with OnTap 9.7, we might still have the same error.

In this case, the quota resize cron job is the workaround until we upgrade the filer to OnTap 9.8.

[Jascha-N]

I have created a cronjob under my own user account, which resizes the quota every hour, 30 minutes past the hour. Maybe this solves the problem. If you prefer to have it in the root crontab, you can move it there, but I'd rather not mess around with that myself.