## Search

Institute for Advanced Simulation (IAS)

# What data quotas do exist and how to list usage?

For all data repositories the disk quota managing is enabled. The values are set to default values (defined by JSC) or depend on special requirements by the projects.

Default data quota per user/project within GPFS file systems

File System

Disk Space

Number of Files

Soft LimitHard Limit Soft LimitHard Limit
$HOME10 GB11 GB10.00011.000$SCRATCH90 TB95 TB4 Mio4.4 Mio
$PROJECT16 TB17TB3 Mio3.1 Mio$FASTDATAdependdependdependdepend
$DATAdependdependdependdepend$ARCHIVE- (see note)500.000550.000

Note:
No hard disk space limit for $ARCHIVE exists. Furthermore for some projects there may exist special guidelines. File size limit Although the file size limit on operation system level e.g. at JUWELS or JURECA is set to unlimited (ulimit -f) the maximum file size can only be the GPFS group quota limit for the corresponding file system. The actual limits can be listed by jutil. List data quota and usage by project or user Members of a group/project can display the hard limits, quotas (soft limit) and usage by each user of the project using the jutil command. jutil project dataquota -p <project name> The quota information for the users are updated once a day. To get the in time quota usage for$SCRATCH, $PROJECT,$FASTDATA and $DATA you must run the GPFS command mmlsquota [--block-size {m|g|t|auto}] -j <project> <project | scratch | fastdata | largedata> For the$ARCHIVE use the option -g <project>

mmlsquota [--block-size {m|g|t|auto}] -g <project> <arch | arch2>

On \$HOME each user has its own quota. The command here is

mmlsquota [--block-size {m|g|t|auto}] -u <userid> home

Some notes on the command output:

• The soft limit is the quota value of the project/user. If the usage exceeds it, the grace period starts (14 days).
• No user/project can use more than defined as hard limit. Writing/appending will be blocked by the operating system.
• The column grace reports the status of the quota

none - no quota exceeded
xdays - remaining grace period to clean up after the soft limit is exceeded
expired - no data can be written before cleanup

Recommendation for users with a lot of small files

Users with applications that create a lot of relatively small files should reorganize the data by collecting these files within tar-archives using the

tar -cvf archive-filename ...

command. The problem is really the number of files (inodes) that have to be managed by the underlying operating system and not the space they occupy in total. On the other hand please keep in mind the recommendations under File size limit.