[gpfsug-discuss] question on fileset / quotas

Markus Rohwedder rohwedder at de.ibm.com
Mon Feb 11 09:36:06 GMT 2019


There is no hierarchy between fileset quotas, the fileset quota limits are
completely independent of each other.
The independent fileset., as you mentioned, provides the common inode space
and ties the parent and child together in regards to
using inodes from their common inode space and for example in regards to
snapshots and other features that act on independent filesets.

There are however many degrees of freedom in setting up quota
configurations, for example user and group quotas and the per-fileset and
per-filesystem quota options.
So there may be other ways how you could create rules that can model your
environment and which could provide a means to create limits across several

For example (will probably not match to you but just to illustrate)::
You have a group of applications.
Each application stores data in one dependent fileset. The filesystem where
these exist uses per filesystem quota accounting.-
All these filesets are children of an independent filesets. this allows you
to  create snapshots of all applications together.
All applications store data under the same group.
You can limit each applications space via fileset quota and you can limit
the whole application group via group quota.

Mit freundlichen Grüßen / Kind regards

Dr. Markus Rohwedder

Spectrum Scale GUI Development
 Phone:  +49 7034 6430190      IBM Deutschland Research &                          
 E-Mail: rohwedder at de.ibm.com  Am Weiher 24                                        
                               65451 Kelsterbach                                   

From:	Imam Toufique <techie879 at gmail.com>
To:	gpfsug-discuss at spectrumscale.org
Date:	09.02.2019 02:42
Subject:	[gpfsug-discuss] question on fileset / quotas
Sent by:	gpfsug-discuss-bounces at spectrumscale.org

Hi Everyone,

I am very new to GPFS, just got the system up and running, now starting to
get myself setting up filesets and quotas.  I have a question, may be in
has been answered already, somewhere in this forum, my apologies for that
if this is a repeat.

My question is:

lets say I have an independent fileset called '/mmfs1/crsp_test' , and I
set it's quota to 2GB ( quota type FILESET ).

STAGING-itoufiqu at crspoitdc-mgmt-001:/mmfs1/crsp_test/itoufiqu$ df
-h /mmfs1/crsp_test/
Filesystem      Size  Used Avail Use% Mounted on
mmfs1           2.0G     0  2.0G   0% /mmfs1

Now, I go create a 'dependent' fileset calld 'itoufiqu' under
'crsp_test' , sharing it's inode space, and i was able to set it's quota to

STAGING-root at crspoitdc-mgmt-001:/mmfs1/crsp_test$ df
-h /mmfs1/crsp_test/itoufiqu
Filesystem      Size  Used Avail Use% Mounted on
mmfs1           4.0G  4.0G     0 100% /mmfs1

Now, i assume that setting quota of 4GB ( whereas the independent fileset
quota is 2GB ) for the above dependent fileset ( 'itoufiqu' ) is being
allowed as dependent fileset is sharing inode space from the independent

Is there a way to setup an independent fileset so that it's dependent
filesets cannot exceed its quota limit? Another words, if my independent
fileset quota is 2GB, I should not be allowed to set quotas for it's
dependent filesets more then 2GB  ( for the dependent filesets created in
aggregate ) ?

Thanks for your help!
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20190211/e5742368/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20190211/e5742368/attachment-0006.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 19326261.gif
Type: image/gif
Size: 4659 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20190211/e5742368/attachment-0007.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20190211/e5742368/attachment-0008.gif>

More information about the gpfsug-discuss mailing list