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 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 base directory shown by POSIX commands (like getent passwd) or in the environment variables can be a symbolic link (e.g. /user), which points to the actual base directory on the data store (e.g. /mnt/vast-nhr/home), or another link farm (/mnt/vast-orga) which only contains symlinks to the real home directories.

The HOME directory is meant 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
• Is regularly backed up to tape (most also have snapshots, see below)
• 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.

Snapshots

If you accidentally deleted or overwrote something in your home directory and want to restore an earlier version of the affected files, it is not always necessary to write a ticket. Most of our home filesystems save regular snapshots that are kept for a short period (between a few days up to 3-4 weeks). These snapshots can be accessed for any directory by entering the hidden .snapshot directory by cd .snapshot.