Please periodically check whether your scientific results data stored on HLRN 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 of the HLRN resources needs to be limited.
The HLRN supports three different file systems for the users, see also File Systems.
- HOME
- for a higher number of files
- limited disk space
- backup
- WORK
- for a moderate number of files
- more disk space, transient nature of data
- no backup, no disaster recovery
- PERM
- secure file system location on magnetic tapes
- no solution for long-term data archiving
- no guarantee for 10 years according to rules for good scientific practice
Check your quota
Check your disk quota limits using the command hlrnquota
. If your user ID is member of one or more project groups you will also get quota information for these project groups. Each of your files and directories is owned by your user ID (user ownership) and by exactly one of the group IDs you are a member in (group ownership). The data base for the output of hlrnquota
is updated twice per hour.
blogin4:~ $ hlrnquota 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
File system quotas at HLRN are enforced
- on HOME and WORK with respect to group ownerships
- on PERM with respect to user ownerships
Quota on HOME and WORK
For each file and directory stored on the HOME and WORK file systems, its group ownership affects the disk quotas of that particular group – no matter where the file or directory itself is located in a given file system. Sometimes this can make it hard to track down the disk quota when files or directories of a given group ownership are distributed over different top-level user directories and/or project directories.
Each user ID is member of one or more groups. Group memberships can be checked with the groups
command.
blogin4:~ $ groups myaccount myaccount prj00012
When, for example, you decide to change the group ownership of a file to prj00012
, the size of this file will affect the disk quota of group prj00012
.
blogin4:~ $ chgrp prj00012 somefile.txt blogin4:~ $ ls -l somefile.txt -rw------- 1 myaccount prj00012 237271040 Jul 3 2020 somefile.txt
blogin4:~ $ chgrp --recursive prj00012 somedirectory blogin4:~ $ ls -ld somedirectory drwx------ 1 myaccount prj00012 4096 Jul 3 2020 somedirectory
General hints on resolving quota issues
As described in File Systems the default quota limits are reasonable for average use cases.
For projects requiring higher quota limits we kindly ask you to contact your consultant to discuss your needs and how we can help you.
Please keep in mind that the overall performance of a global parallel file system depends on the free capacity (better performance with high free capacity).
HOME quota exceeded
The HOME file system (HOME=/home/${USER}
) is intended to be used for the following data:
- configuration files
- source code and executables
- important files for backup
You might experience an exceeded HOME quota due to unintended usage of the HOME file system, e.g.
- large files
- parallel input/output for your jobs
If your HOME quota is exceeded, we recommend
- to check whether you can either delete files or move files from HOME to WORK (no backup!) or to PERM
- to contact your consultant, explain your storage needs, and ask for a higher quota limits.
WORK quota exceeded
The WORK file system (in WORK=/scratch/usr/${USER}
or /scratch/projects/<projectID>
) is intended to be used for the following data:
- large files
- parallel input/output for your jobs
If your WORK quota is exceeded, we recommend
- to check whether you can delete files or move files from WORK to PERM
- to change the group ownership of files to "move" their attribution from the quota of your primary group (user ID) to the quota of another group (e.g.
prj00012
) - to contact your consultant, explain your storage needs, and ask for higher quota limits.