Hi All,

We had 3 local GPFS filesystems on our cluster … let’s call them gpfs0, gpfs1, 
and gpfs2.  gpfs0 is for project space (i.e. groups can buy quota in 1 TB 
increments there).  gpfs1 is scratch and gpfs2 is home.

We are combining gpfs0 and gpfs1 into one new filesystem (gpfs3) … we’re doing 
this for multiple reasons that aren’t really pertinent to my question here, but 
suffice it to say I have discussed our plan with some of IBM’s GPFS people and 
they agree that it’s the thing for us to do.

gpfs3 will have a scratch fileset with no fileset quota, but user and group 
quotas (just like the gpfs1 filesystem currently has).  We will also move all 
the filesets from gpfs0 over to gpfs3 - those use fileset quotas only - no user 
or group quotas.

I have created the new gpfs3 filesystem, the scratch fileset within it, and one 
of the project filesets coming over from gpfs0.  I’ve also moved my scratch 
directory to the gpfs3 scratch fileset.  When I run mmlsquota I see (please 
note, I’ve changed names of things to protect the guilty):

kevin@gateway: mmlsquota -u kevin --block-size auto
                         Block Limits                                    |     
File Limits
Filesystem type         blocks      quota      limit   in_doubt    grace |    
files   quota    limit in_doubt    grace  Remarks
gpfs0     USR         no limits

                         Block Limits                                    |     
File Limits
Filesystem type         blocks      quota      limit   in_doubt    grace |    
files   quota    limit in_doubt    grace  Remarks
gpfs1     USR          2.008G        50G       200G          0     none |       
 3  100000  1000000        0     none

                         Block Limits                                    |     
File Limits
Filesystem type         blocks      quota      limit   in_doubt    grace |    
files   quota    limit in_doubt    grace  Remarks
gpfs2     USR          11.69G        25G        35G          0     none |     
8453  100000   200000        0     none

                         Block Limits                                           
    |     File Limits
Filesystem Fileset    type         blocks      quota      limit   in_doubt    
grace |    files   quota    limit in_doubt    grace  Remarks
gpfs3     root       USR         no limits
gpfs3     scratch    USR          31.04G        50G       200G          0     
none |     2134  200000  1000000        0     none
gpfs3     fakegroup  USR         no limits
kevin@gateway:

My question is this … why am I seeing the “root” and “fakegroup” filesets 
listed in the output for gpfs3?  They don’t show up for gpfs0 and the also 
exist there.

Is it possibly because there are no user quotas whatsoever for gpfs0 and there 
are user quotas on the gpfs3:scratch fileset?  If so, that still doesn’t make 
sense as to why mmlsquota would think it needs to show the filesets within that 
filesystem that don’t have user quotas.  In fact, we don’t *want* that to 
happen, as we have certain groups that deal with various types of restricted 
data and we’d prefer that their existence not be advertised to everyone on the 
cluster.

Oh, we’re still in the process of upgrading clients on our cluster, but this 
output is from a client running 4.2.2.1, in case that matters.  Thanks all...
—
Kevin Buterbaugh - Senior System Administrator
Vanderbilt University - Advanced Computing Center for Research and Education
[email protected]<mailto:[email protected]> - 
(615)875-9633



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

Reply via email to