If your project needs larger quotas, please contact your consultant to discuss your needs and how we can help you.

Please visit File Systems for the properties of the file systems HOME, WORK, and PERM.

Please periodically check whether your scientific results data stored on the file systems should be periodically transferred to the user's home institution. To maintain good I/O performance for all user jobs, the usage of the shared file systems for all resources needs to be limited.

Quota defaults

The default values for user quota are reasonable for average use cases. We are aware that certain projects need larger quota for their workflows. If your project needs larger quotas, please contact your consultant to discuss your needs and how we can help you.

File system quotas are enforced

• on HOME and WORK with respect to their parent directory "name": /home/${NAME}, /scratch/usr/{NAME}, or /scratch/projects/{NAME} (Technically, this is implemented by GPFS filesets.)
• on PERM with respect to user ownerships

^✦ there is user ownership only

Quota is available on the three file systems HOME, WORK and PERM. On each file system we distinguish

• quota for blocks, that is the disk space your files allocate, and
• quota for inodes, that is the number of files and directories.

Each quota consists of two numbers, the soft limit and the hard limit.

• Once your usage achieves the soft limit, the grace period of 2 weeks starts to count. By the end of the grace period you are not able to write files. As soon as you drop down below your soft limit the grace period is reseted.
• Once your usage achieves the hard limit, you are not able to write files.

Check your quota

Check your disk quota limits using the command show-quota. If your user ID is member of one or more project groups you will also get quota information for these project groups. The data base for the output of show-quota is updated twice per hour.

blogin7:~ $ show-quota
Home
                           Blocks used   Soft limit   Hard limit     Inodes used   Soft limit   Hard limit    
  myaccount  (users)          89.45 GiB       40 GiB      100 GiB         187.3 k            -            -    
  prj00012  (projects)        68.03 GiB       40 GiB      100 GiB         659.6 k            -            -    

Work
                           Blocks used   Soft limit   Hard limit     Inodes used   Soft limit   Hard limit    
  myaccount  (users)          1.202 TiB        3 TiB       30 TiB          1.74 k        250 k        1.5 M    
  prj00012  (projects)        2.512 TiB       12 TiB       30 TiB               1          1 M          6 M    

Fixing quota issues

If your HOME quota is exceeded, we recommend

1. to check whether you can either delete files or move files from HOME to WORK (no backup!) or to PERM
2. to contact your consultant, explain your storage needs, and ask for a higher quota limits.

If your WORK quota is exceeded, we recommend

1. to check whether you can delete files or move files from WORK to PERM
2. to move files between parent directories, e.g. from your private work /scratch/usr/{NAME} to a compute project /scratch/projects/{NAME} (NAME defines where the quota is accounted.)
3. to contact your consultant, explain your storage needs, and ask for higher quota limits.

Sometimes this can make it hard to track down the disk quota when files or directories are distributed over different user and/or project directories.
However, all quota related to you has to be located either in your personal directories:

• /home/${USER}
• /scratch/usr/${USER}

or in one of the projects folders you are a member of:

• /scratch/projects/<projectID>
  
• /scratch/share/<projectID>

All possible memberships are listed by typing: groups

Blocks / disk space exeeded

Once you experience too many Blocks you should check for disk usage in a directory.

blogin4:~ $ du -sh /home/myaccount/somedirectory
1.4G /home/myaccount/somedirectory
blogin4:~ $ du -sh /home/myaccount/somedirectory/*
227M /home/myaccount/somedirectory/subdir1
627M /home/myaccount/somedirectory/subdir2
...

Inodes / files number exeeded

Once you experience too many Inodes you should count the number of files in a directory.

blogin4:~ $ find /home/myaccount/somedirectory | wc -l

Related articles

• Seite:
  Sharing data
• Seite:
  File Systems
• Seite:
  System Quota
• Seite:
  Metadata Usage on WORK
• Seite:
  Unspecific error messages when reading huge input files