[gpfsug-discuss] Working with per-fileset quotas

[Oesterlin, Robert]

Looking at the default case in a new file system/fileset, if you did an “mmrepquota” you’d see everyone have a default quota of zero. Meaning – any time you set a user/fileset/group quota back to zero, you are removing any trace of the previous quota. On you your specific question - yes, one by one is it, I’m not aware of any other way to do it.

Hard quota set, no soft quota: no grace period
Hard Soft quota set and equal: no grace period
Hard quota set or unset, soft quota set: grace period

The default behavior is no grace period unless soft quota is set, maybe that’s why it’s no displayed?


Bob Oesterlin
Sr Principal Storage Engineer, Nuance

From: <gpfsug-discuss-bounces at spectrumscale.org> on behalf of Keith Ball <bipcuds at gmail.com>
Reply-To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: Saturday, December 9, 2017 at 3:50 PM
To: "gpfsug-discuss at spectrumscale.org" <gpfsug-discuss at spectrumscale.org>
Subject: [EXTERNAL] Re: [gpfsug-discuss] Working with per-fileset quotas

I meant more specifically, remove any indication that quotas have been set, for anyone (or everyone). That way, I could have a script to clean out old quota definitions, then set both default and explicit quotas, without any old settings lurking around. Is there a way to get rid of (e.g. zero out) all existing explicit PER-FILESET quota definitions, and start over (without having to look at mmrepquota and zero them out one by one)?


So I see your point about soft=lard limit => no grace period. I guess what's odd is that I see any indication that the grace period is not "none"; what grace period would be assigned to a per-fileset quota if I cannot even view or set it?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20171210/5b19346b/attachment.htm>