[gpfsug-discuss] Quota: revert user quota to FILESET default

Popescu, Razvan rp2927 at gsb.columbia.edu
Tue Jan 7 19:39:22 GMT 2020 

Thank you very much, Kuei.  It’s now clear where we stand, even though I would have liked to have that added selectivity in mmedquota.

We use filesets to separate classes of projects and classes of storage (backup/noBackup for example), and thus one user or one group(=project), has various resource allocations across filesets (enforced by quotas).  Sometimes we need to roll back only certain allocations and leave other untouched ….
If no one else encountered this need so far, I guess we twisted the model a bit too much 😊.

Maybe we can add this option to some list of desired new features for coming versions?...


Thanks,
Razvan

--


From: Kuei-Yu Wang-Knop <kywang at us.ibm.com>
Date: Tuesday, January 7, 2020 at 2:13 PM
To: "Popescu, Razvan" <rp2927 at gsb.columbia.edu>
Cc: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: RE: [gpfsug-discuss] Quota: revert user quota to FILESET default


Razvan,

You are right, the command below yields to an error (as it interprets fs9:fset7 as a user name). Apologies for the confusion.

This is what I see in my system:

# mmedquota -d -u pfs004 fs9:fset7
fs1 USR default quota is off
fs9:fset7 is not valid user
#

I must have confused the command names in the previous note. Instead of "mmedquota -d" command I meant "mmlsquota -d" (??)
# mmlsquota -d fs9:fset7
Default Block Limits(KB) | Default File Limits
Filesystem Fileset type quota limit | quota limit entryType
fs9 fset7 USR 102400 1048576 | 10000 0 default on
fs9 fset7 GRP 0 0 | 0 0 i
# mmlsquota -d fs9:fset9
Default Block Limits(KB) | Default File Limits
Filesystem Fileset type quota limit | quota limit entryType
fs9 fset9 USR 102400 1048576 | 10000 22222 default on
fs9 fset9 GRP 0 0 | 0 0 default off
#mmlsquota -d -u fs9
Default Block Limits(KB) | Default File Limits
Filesystem type quota limit | quota limit Remarks
fs9 USR 102400 1048576 | 10000 0
#

Upon further investigation, the current behavior of 'mmedquota -d -u <username>' is restore the default quotas for the particular user on all filesystems and filesets. The ability to restore the default limits of a user for selected filesets and filesystems is not available at the moment.

Kuei

------------------------------------
Kuei-Yu Wang-Knop
IBM Scalable I/O development
(845) 433-9333 T/L 293-9333, E-mail: kywang at us.ibm.com


[Inactive hide details for "Popescu, Razvan" ---01/07/2020 12:23:47 PM---Kuei, Thanks for replying.   I did open a ticket before]"Popescu, Razvan" ---01/07/2020 12:23:47 PM---Kuei, Thanks for replying. I did open a ticket before the holidays, but it didn’t yield a solution

From: "Popescu, Razvan" <rp2927 at gsb.columbia.edu>
To: Kuei-Yu Wang-Knop <kywang at us.ibm.com>, gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: 01/07/2020 12:23 PM
Subject: [EXTERNAL] Re: [gpfsug-discuss] Quota: revert user quota to FILESET default
________________________________



Kuei,

Thanks for replying. I did open a ticket before the holidays, but it didn’t yield a solution. I just opened another one…

My very specific question to you is: “Where have you seen this particular syntax work?” The 5.0.3 & 5.0.4 mmedquota man pages do not mention the availability of a filesystem:fileset parameter (as in your example: “fs9:fset7”) and my testing rejected such a parameter. What made you think this would work? ?

# mmedquota -d -u pfs004 fs9:fset7
^^^^^^^^^^^^^

Many thanks!
Razvan

--


From: Kuei-Yu Wang-Knop <kywang at us.ibm.com>
Date: Tuesday, January 7, 2020 at 12:11 PM
To: "Popescu, Razvan" <rp2927 at gsb.columbia.edu>, gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: RE: [gpfsug-discuss] Quota: revert user quota to FILESET default

Razvan,

Perhaps you should open a ticket (so that specific configuration data could be collected and analyzed) on this topic. We would look at your system configuration, the code level to figure out whether what you are seeing is a problem or it is just an expected behavior or a limitation; there are some limitations, specifically moving default limits between file system and fileset default scope, that may not work for your scenario.

Thanks,

Kuei
------------------------------------
Kuei-Yu Wang-Knop
IBM Scalable I/O development
(845) 433-9333 T/L 293-9333, E-mail: kywang at us.ibm.com


[Inactive hide details for "Popescu, Razvan" ---01/07/2020 11:32:42 AM---Hi Kuei-Yu (et al.) Happy New Year!]"Popescu, Razvan" ---01/07/2020 11:32:42 AM---Hi Kuei-Yu (et al.) Happy New Year!

From: "Popescu, Razvan" <rp2927 at gsb.columbia.edu>
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: 01/07/2020 11:32 AM
Subject: [EXTERNAL] Re: [gpfsug-discuss] Quota: revert user quota to FILESET default
Sent by: gpfsug-discuss-bounces at spectrumscale.org

________________________________




Hi Kuei-Yu (et al.)

Happy New Year!

I’d like to reiterate my follow-up question to your comments – in particular to the line copied below, which mentions a behavior that I’m seeking for this command, but cannot reproduce (in vers, 5.0.3 at Linux), namely (with my highlights):

# mmedquota -d -u pfs004 fs9:fset7 <=== run mmedquota -d -u to get default limits

The reduction of scope to a named filesystem/fileset is what I’m seeking, *but* at least the 5.0.3 version seems to reject that parameter with an error, and apply the user’s default restoration to *all filesystems and filesets*
Are you using a different version? Or a different implementations? I’m running SS 5.0.3 on Linux x64.

I apologize for having to press this point, but this matter is of a certain importance to us and it appears that the public documentation is mum in this regard. Furthermore, the IBM support, at the first pass, was quite confused and unfocused. (I’m trying with a new case now, but my hopes are low). You seem to be an IBM insider, so …. I count on your help ?. Sorry, for the insistence. ?

Best,

Razvan Popescu

Columbia Univ.

--


From: <gpfsug-discuss-bounces at spectrumscale.org> on behalf of Kuei-Yu Wang-Knop <kywang at us.ibm.com>
Reply-To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: Thursday, December 19, 2019 at 3:56 PM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: Re: [gpfsug-discuss] Quota: revert user quota to FILESET default

Razvan,

mmedquota -d -u fs:fset:

-d
Reestablish default quota limits for a specific user, group, or fileset that had an explicit quota limit set by a previous invocation of the mmedquota command.
This option will assign the default quota to the user. The quota entry type will change from "e" to "d_fset". You may need to play a little bit with your system to get the result as you can have default quota per file system set and default quota per fileset enabled.

An exemple to illustrate

User pfs004 in filesystem fs9 and fileset fset7 has explicit quota set:

# mmrepquota -u -v fs9 | grep pfs004
pfs004 fset7 USR 1088 102400 1048576 0 none | 13 10000 33333 0 none e <=== explicit


# mmlsquota -d fs9:fset7
Default Block Limits(KB) | Default File Limits
Filesystem Fileset type quota limit | quota limit entryType
fs9 fset7 USR 102400 1048576 | 10000 0 default on <=== default quota limits for fs9:fset7, the default
fs9 fset7 GRP 0 0 | 0 0 i


# mmlsquota -u pfs004 fs9:fset7
Block Limits | File Limits
Filesystem Fileset type KB quota limit in_doubt grace | files quota limit in_doubt grace Remarks
fs9 fset7 USR 1088 102400 1048576 0 none | 13 10000 33333 0 none <=== explicit

# mmedquota -d -u pfs004 fs9:fset7 <=== run mmedquota -d -u to get default limits

# mmlsquota -u pfs004 fs9:fset7
Block Limits | File Limits
Filesystem Fileset type KB quota limit in_doubt grace | files quota limit in_doubt grace Remarks
fs9 fset7 USR 1088 102400 1048576 0 none | 13 10000 0 0 none <=== takes the default value


# mmrepquota -u -v fs9:fset7 | grep pfs004
pfs004 fset7 USR 1088 102400 1048576 0 none | 13 10000 0 0 none d_fset <=== now user pfs004 in fset7 takes the default limits
#


------------------------------------
Kuei-Yu Wang-Knop
IBM Scalable I/O development
(845) 433-9333 T/L 293-9333, E-mail: kywang at us.ibm.com


[Inactive hide details for "Popescu, Razvan" ---12/19/2019 02:28:51 PM---I see. May I ask one follow-up question, please:   what]"Popescu, Razvan" ---12/19/2019 02:28:51 PM---I see. May I ask one follow-up question, please: what is “mmedquota -d -u <username>” supposed

From: "Popescu, Razvan" <rp2927 at gsb.columbia.edu>
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: 12/19/2019 02:28 PM
Subject: [EXTERNAL] Re: [gpfsug-discuss] Quota: revert user quota to FILESET default
Sent by: gpfsug-discuss-bounces at spectrumscale.org
________________________________





I see.

May I ask one follow-up question, please: what is “mmedquota -d -u <username>” supposed to do in this case?

Really appreciate your assistance.

Razvan

--


From: <gpfsug-discuss-bounces at spectrumscale.org> on behalf of Kuei-Yu Wang-Knop <kywang at us.ibm.com>
Reply-To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: Thursday, December 19, 2019 at 2:25 PM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: Re: [gpfsug-discuss] Quota: revert user quota to FILESET default

>> To make it more technical …. This fellow’s quota entryType is now “e” . I want to change it back to entryType “I”. (I hope I’m not talking nonsense here)

Currently there is no function to revert an explicit quota entry (e) to initial (i) entry.

Kuei
------------------------------------
Kuei-Yu Wang-Knop
IBM Scalable I/O development
(845) 433-9333 T/L 293-9333, E-mail: kywang at us.ibm.com


[Inactive hide details for "Popescu, Razvan" ---12/19/2019 02:18:54 PM---Thanks for your kind reply. My problem is different tho]"Popescu, Razvan" ---12/19/2019 02:18:54 PM---Thanks for your kind reply. My problem is different though.

From: "Popescu, Razvan" <rp2927 at gsb.columbia.edu>
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: 12/19/2019 02:18 PM
Subject: [EXTERNAL] Re: [gpfsug-discuss] Quota: revert user quota to FILESET default
Sent by: gpfsug-discuss-bounces at spectrumscale.org

________________________________






Thanks for your kind reply.

My problem is different though.

I have set a fileset default quota (doing all the steps you recommended) and all was Ok. During operations I have edited *individual* quotas, for example to increase certain user’s allocations.

Now, I want to *revert* (change back) one of these users to the (fileset) default quota !

For example, I have used one user account to test the mmedquota command setting his limits to a certain value (just testing). I’d like now to make that user’s quota be the default fileset quota, and not just numerically, but have his quota record follow the changes in fileset default quota limits.

To make it more technical …. This fellow’s quota entryType is now “e” . I want to change it back to entryType “I”. (I hope I’m not talking nonsense here)

mmedquota’s “-d” option is supposed to reinstate the defaults, but it doesn’t seem to work for fileset based quotas … !?!

Razvan

--


From: <gpfsug-discuss-bounces at spectrumscale.org> on behalf of Kuei-Yu Wang-Knop <kywang at us.ibm.com>
Reply-To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: Thursday, December 19, 2019 at 2:06 PM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: Re: [gpfsug-discuss] Quota: revert user quota to FILESET default

It sounds like you would like to have default perfileset quota enabled. Have you tried to enable the default quota on the filesets and then set the default quota limits for those filesets?

For example, in a filesystem fs9 and fileset fset9. File system fs9 has default quota on and --perfileset-quota enabled.
# mmlsfs fs9 -Q --perfileset-quota
flag value description
------------------- ------------------------ -----------------------------------
-Q user;group;fileset Quotas accounting enabled
user;fileset Quotas enforced
user;group;fileset Default quotas enabled
--perfileset-quota Yes Per-fileset quota enforcement

#


Enable default user quota for fileset fset9, if not enabled yet,

e.g. "mmdefquotaon -u fs9:fset9"

Then set the default quota for this fileset using mmdefedquota"
# mmdefedquota -u fs9:fset9

..
*** Edit quota limits for USR DEFAULT entry for fileset fset9
NOTE: block limits will be rounded up to the next multiple of the block size.
block units may be: K, M, G, T or P, inode units may be: K, M or G.
fs9: blocks in use: 0K, limits (soft = 102400K, hard = 1048576K)
inodes in use: 0, limits (soft = 10000, hard = 22222)

...


Hope that this helps.


------------------------------------
Kuei-Yu Wang-Knop
IBM Scalable I/O development
(845) 433-9333 T/L 293-9333, E-mail: kywang at us.ibm.com


[Inactive hide details for "Popescu, Razvan" ---12/19/2019 12:22:34 PM---Hi, I’d like to revert a user’s quota to the fileset]"Popescu, Razvan" ---12/19/2019 12:22:34 PM---Hi, I’d like to revert a user’s quota to the fileset’s default, but “mmedquota -d -u <username>”

From: "Popescu, Razvan" <rp2927 at gsb.columbia.edu>
To: "gpfsug-discuss at spectrumscale.org" <gpfsug-discuss at spectrumscale.org>
Date: 12/19/2019 12:22 PM
Subject: [EXTERNAL] [gpfsug-discuss] Quota: revert user quota to FILESET default
Sent by: gpfsug-discuss-bounces at spectrumscale.org
________________________________







Hi,

I’d like to revert a user’s quota to the fileset’s default, but “mmedquota -d -u <username>” fails because I do have not set a filesystem default….
[root at xxx]# mmedquota -d -u user
gsb USR default quota is off

(SpectrumScale 5.0.3 Standard Ed. on RHEL7 x86)

Is this a limitation of the current mmedquota implementation, or of something more profound?...

I have several filesets within this filesystem, each with various quota structures. A filesystem-wide default quota didn’t seem useful so I never defined one; however I do have multiple fileset-level default quotas, and this is the level at which I’d like to be able to handle this matter… Have I hit a limitation of the implementation? Any workaround, if that’s the case?

Many thanks,

Razvan Popescu
Columbia Business School
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss



_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss



_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss



_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss







-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20200107/28fee43d/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 106 bytes
Desc: image001.gif
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20200107/28fee43d/attachment-0010.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.gif
Type: image/gif
Size: 107 bytes
Desc: image002.gif
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20200107/28fee43d/attachment-0011.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.gif
Type: image/gif
Size: 108 bytes
Desc: image003.gif
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20200107/28fee43d/attachment-0012.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.gif
Type: image/gif
Size: 109 bytes
Desc: image004.gif
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20200107/28fee43d/attachment-0013.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.gif
Type: image/gif
Size: 110 bytes
Desc: image005.gif
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20200107/28fee43d/attachment-0014.gif>

More information about the gpfsug-discuss mailing list