Purpose

The purpose of the “myquota” command is to enable end-users to query allocated limits and current usage of relevant disk quota. The tool simplifies obtaining such an up-to-date overview, tailored to the calling end-user, with virtually no effort on the part of the user.

  • The output format of the different types of quota (for home, scratch, and project spaces) has been made uniform in that usage is consistently displayed as a percentage of quota limits—unless no limits have been set.
  • Since scratch and home quota are 'personal,' in that they are user quotas pertaining to the files that a user owns on a particular file system, they are automatically displayed for the calling user.
  • The command has built-in help that is displayed by invoking the command with the “--help” option.

If you see that you are near or at your quota, you might be interested in this tutorial on how to efficiently clean up your home directory or project space.


Project spaces are not included by default in the output of myquota. However, users can customize what specific project space(s) to include in the overview by naming them in an environment variable: “MYQUOTA_PROJECTSPACES”:

# Include two project spaces in the myquota output
snellius paulm@int4 17:19 ~$ MYQUOTA_PROJECTSPACES="viz ebsrc" myquota
paulm@home4
  Quota                Limit                Usage
  400.00 GiB           410.00 GiB           87.1158%        GiB        [==========================    ]
  2000000 Inodes       2100000 Inodes       64.0827%        Inodes     [===================           ]


paulm@wstor_scratch1
  Quota                Limit                Usage
  8.00 TiB             10.00 TiB            0.0131%         TiB        [                              ]
  3000000 Inodes       4000000 Inodes       7.4781%         Inodes     [==                            ]


ebsrc@wstor_work4
  Quota                Limit                Usage
  1.00 TiB             1.00 TiB             95.3730%        TiB        [============================  ]
  1000000 Inodes       1100000 Inodes       3.2764%         Inodes     [                              ]


viz@wstor_work4
  Quota                Limit                Usage
  10.00 TiB            10.00 TiB            47.3264%        TiB        [==============                ]
  1728141 Inodes       1900955 Inodes       72.0614%        Inodes     [=====================         ]


How to use it

myquota

usage: myquota [-h] [--autodetect] [PROJECT ...]

Display GPFS quota information for home, scratch and project spaces.
Project spaces that should always be checked can be stored in the
environment variable 'MYQUOTA_PROJECTSPACES', (e.g. "export
MYQUOTA_PROJECTSPACES='prjs0123 prjs4567'").

positional arguments:
  PROJECT       project spaces to check (e.g., prjs0123)

optional arguments:
  -h, --help    show this help message and exit
  --autodetect  enable auto-detection of project spaces associated
                with your budget account

Description:

List home and scratch quota and usage pertaining to the current user, and optionally also list project space quota for any specified project space of interest to you. Instead of specifying any project spaces on the command line, a (space-separated list of) project space(s) can also be stored in the environment variable “MYQUOTA_PROJECTSPACES”. If this variable is non-empty and command-line arguments are specified as well, the specified command-line arguments overrule the contents of the environment variable. In this way, you can easily customize the default working of the myquota by adding an export statement in your login profile, like so:

export MYQUOTA_PROJECTSPACES="project_x project_y".

Note that there is no need to use the complete pathname. Since we insist on unique project space names across file systems, just the basename(s) will do. 

Additionally, there is a “--autodetect” option that queries the accounting system for any project spaces that are associated with your budget account. This query is relatively slow and it is unable to detect project spaces that you have access to and are associated with another budget account. It's therefore recommended to use the “MYQUOTA_PROJECTSPACES” variable for project spaces that you'd like to check regularly, or to pass the project spaces to the myquota command as arguments.

  • No labels