HOME
Every user gets a HOME directory.
Its path is always stored in the environmental variable HOME and most shells will expand ~ into it.
The directory will be HOME_BASE/ACADEMIC_CLOUD_USERNAME/USER for members of projects in the HPC Project Portal and HOME_BASE/USER otherwise (e.g. legacy NHR/HLRN accounts), where HOME_BASE is one of the base directories for home directories (there is more than one and they may change in the future).
The HOME directory is for a user’s
- configuration files
- source code
- self-built software
The HOME storage systems have the following characteristics:
- Optimized for a high number of files rather than capacity
- Optimized for robustness rather than performance
- Has limited disk space per user
- Backed up (some also have snapshots found at
HOME_BASE/.snapshots) - Has a quota
The HOME filesystems have slow-medium to medium performance. The HOME directories for each kind of user are given in the table below.
| Kind of User | Media | Capacity | Filesystem |
|---|---|---|---|
| NHR | SSD | 1.15 PiB (shared)(comp)(dedup) | VAST exported via NFS |
| SCC (HPC Project Portal users) | SSD | 1.15 PiB (shared)(comp)(dedup) | VAST exported via NFS |
| SCC (legacy) | HDD | 10.5 PiB | Stornext exported directly and via NFS |
| KISSKI | SSD | 1.15 PiB (shared)(comp)(dedup) | VAST exported via NFS |
| REACT | SSD | 1.15 PiB (shared)(comp)(dedup) | VAST exported via NFS |
Ones marked with “(shared)” in their capacity share space with other data stores. For example, NHR HOME and Project data stores are on the storage system.
Ones marked with “(comp)” use live compression to increase effective capacity, though this comes at the expense of some CPU time to compress and decompress.
Ones marked with “(dedup)” use deduplication to increase effective capacity.