- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -
- Information contained in the HLRS Wiki is not legally binding and HLRS is not responsible for any damages that might result from its use -
Storage (Hawk): Difference between revisions
No edit summary |
|||
Line 16: | Line 16: | ||
** Basepath: /lustre/hpe/ws11 | ** Basepath: /lustre/hpe/ws11 | ||
** available storage capacity: 15 PB | ** available storage capacity: 15 PB | ||
** project quota limits: | ** project quota limits: enabled | ||
** max. workspace duration: 60 days | ** max. workspace duration: 60 days | ||
** max. workspace extensions: 3 | ** max. workspace extensions: 3 |
Latest revision as of 12:23, 12 December 2024
HOME Directories
Users' HOME directories are located on a shared RAID system and are mounted via NFS on all login (frontend) and compute nodes. The path to the HOME directories is consistent across all nodes. The filesystem space on HOME is limited by a small quota (50GB per user, 200GB per group)! The quota usage for your account and your groups can be listed using the na_quota command on the login nodes.
In addition, a project volume can be made available on request (see Project_filesystem)
SCRATCH directories / workspace mechanism
For large files and fast I/O Lustre based scratch directories are available which make use of the high speed network infrastructure. Scratch directories are available on all compute and login (frontend) nodes via the WORKSPACE MECHANISM.
Properties of the workspace filesystems on hawk:
- ws11:
- Basepath: /lustre/hpe/ws11
- available storage capacity: 15 PB
- project quota limits: enabled
- max. workspace duration: 60 days
- max. workspace extensions: 3
- lustre devices: 2 MDS, 2 MDT, 20 OSS, 40 OST
- performance: ~200 GiB/s
Each user has access to both filesystems via the WORKSPACE MECHANISM
localscratch
Some special node types (AI nodes, Pre-Post nodes, login nodes, see also node_types ) have a local disk installed and mounted on /localscratch. On this nodes:
- each batchjob creates a /localscratch/$PBS_JOBID directory owned by the job owner.
- each ssh login session creates a /localscratch/$UID directory owned by $UID.
- at the end of a user batch job, the directory $PBS_JOBID in /localscratch on the node will be removed!
- at the end of all login sessions of a user on a node, the $UID directorie in /localscratch will be removed!
- the individual /localscratch filesystem on the nodes is not shared with other nodes.
Filesystem Policy
IMPORTANT! NO BACKUP!! There is NO backup done of any user data located on HWW Cluster systems. The only protection of your data is the redundant disk subsystem. This RAID system is able to handle a failure of one component. There is NO way to recover inadvertently removed data. Users have to backup critical data on their local site! Please see also Storage_usage_policy#Usage_guidelines_for_workspace_filesystems
Long term storage
For data which should be available longer than the workspace time limit allowed and for very important data storage, please use the High Performance Storage System (HPSS)