Project
The Project directories of projects are for
- configuration files
- source code
- self-built software
- medium term data storage
The Project storage systems have the following characteristics:
- Optimized for a high number of files rather than capacity
- Optimized for robustness rather than performance
- Backed up and/or has snapshots
- Has a quota
The Project filesystems have slow-medium to medium performance.
The directory’s symlink in the Project Map directory for each project has the name dir.project.
The Project directories for each kind of project are given in the table below.
| Kind of Project | Path | Media | Capacity | Filesystem |
|---|---|---|---|---|
| SCC | /mnt/ceph-hdd/projects/PROJECT | HDD with metadata on SSD | 21 PiB (shared) | CephFS |
| NHR | /mnt/vast-nhr/projects/PROJECT | SSD | 1.15 PiB (shared)(comp)(dedup) | VAST exported via NFS |
| KISSKI | /mnt/vast-kisski/projects/PROJECT | SSD | 1.15 PiB (shared)(comp)(dedup) | VAST exported via NFS |
| REACT | /mnt/vast-react/projects/PROJECT | SSD | 1.15 PiB (shared)(comp)(dedup) | VAST exported via NFS |
Info
Legend for the tags in the Capacity column:
(shared): They share capacity with other data stores. For example, NHR Project and HOME data stores are on the same storage system.
(comp): Use live compression to increase effective capacity, though this comes at the expense of some CPU time to compress and decompress.
(dedup): Use deduplication to increase effective capacity.
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 generally necessary to write a ticket.
The PROJECT filesystems save regular snapshots that are kept for a short period (currently 30 days of daily snapshots).
These snapshots can be accessed for any directory by entering the hidden .snapshot directory by cd .snapshot.
Info
The .snapshot directories are “hidden” on a deep level, so that they don’t even show up with ls -a, and thus autocomplete on the command line does not work for them.
They are implemented this way on VAST and CephFS filesystems, so they can be accessed everywhere, for every (sub-)directory, and are not included when copying or moving directories to another location.