This page describes how to manage your storage quota on our Lustre and Panasas storage systems.

Determine quota usage on the HPC/Spear (GPFS)

To determine how much of your quota you are using in your HPC or Spear home directory, login and run the following command:

$ gpfs_quota --home

Showing quota information for home dirctory: user
                         Block Limits                                    |     File Limits
Filesystem type         blocks      quota      limit   in_doubt    grace |    files   quota    limit in_doubt    grace  Remarks
home       USR          73.44G       150G       150G         1M     none |    10515       0        0        0     none DSS01.local

To determine how much of your quota your group is using in your purchased research allocation directory, login and run the following command:

$ gpfs_quota [fileset_name]

Showing quota information for research fileset: [filset_name]
                         Block Limits                                    |     File Limits
Filesystem type         blocks      quota      limit   in_doubt    grace |    files   quota    limit in_doubt    grace  Remarks
research   FILESET      3.902T     5.859T     5.859T     6.237G     none |  3139994       0        0    17734     none DSS01.local

Note, if you need more details or a different output format (such as bytes), you can use the mmlsquota command (refer to official documentation for more info on this command):

# Print home directory quota
/usr/lpp/mmfs/bin/mmlsquota home --block-size=auto

# Print research fileset quota
/usr/lpp/mmfs/bin/mmlsquota -j FILESET_NAME research --block-size=auto

Determine storage usage on Archival

Currently, we are working on a solution for users to view storage usage on our Archival system.  In the meantime, you can submit a support request, and we will provide this information.

Which directories or users are using the most storage space?

Within any directory on any filesystem, you can calculate the distribution of storage space used by using the du command.  Warning: This command can take a very long time to run, since it must read the file attributes for every single file in a given directory tree.  It is recommended you run this command in a screen session.

du -ch --max-depth=1 /PATH/TO/ANALYZE