You are located in service: RWTH High Performance Computing (Linux)

File Systems Overview

File Systems Overview

For each CLAIX user and computing time project space is allocated on the CLAIX storage systems to facilitate their research and computational tasks. The cluster offers various file systems, each with its unique advantages and limitations. The appropriate file system for any workflow depends on the task at hand.

You are primarily responsible for backing up your data. The HPC cluster is not intended as a long-term data storage solution. It is crucial to regularly backup data to avoid any potential loss.

The three permanent file systems are as follows:

  • $HOME: Upon logging in, users are directed to their personal home-directory within $HOME. With an integrated backup solution, this file system is particularly well-suited for the storage of important results that are challenging to reproduce, as well as for the development of code projects. However, frequent and massive file transfers, creation, and deletion should be avoided.
  • $WORK: This file system is on the same storage system as $HOME, but has no backup solution.
  • $HPCWORK: This file system is on a different storage system than $HOME and $WORK and offers better I/O performance. In addition, it provides an HDD and a SSD storage pool. By default, all files are stored on the HDD pool. For specific tasks that require very fast I/O, you may use the limited SSD storage.

To switch between the filesystems, use cd $HOME, cd $WORK and cd $HPCWORK.

Some additional key points include:

Overview

In the following table you can see a summary of all and additional details of the available file systems discussed before.

File SystemPathPersistenceSnapshotsBackupQuota (space)Quota (#files)Use Cases
$HOME/home/<username>permanent$HOME_SNAPSHOTyes250 GB1 million

Source code,

configuration files,

important results

$WORK/work/<username>permanent$WORK_SNAPSHOTno250 GB1 millionI/O intensive computing jobs
$HPCWORK/hpcwork/<username>permanent-no1000 GB1 million

I/O intensive computing jobs

large files

$BEEONDstored in $BEEONDtemporary-no

HPC Segment:
1.44 TB/node

ML
Segment
:
635 GB/node

-

I/O intensive computing jobs,

many small working files,

any kind of scratch data

last changed on 01/24/2025

How did this content help you?

(opens in new tab)
This work is licensed under a Creative Commons Attribution - Share Alike 3.0 Germany License (opens in new tab)