- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -

Difference between revisions of "CRAY XE6 Disk Storage"

From HLRS Platforms
Jump to navigationJump to search
Line 1: Line 1:
 
=== HOME Directories ===
 
=== HOME Directories ===
  
All user HOME directories for every compute node of the cluster are located on a shared RAID system. The compute nodes and login node (frontend) have the HOME directories mounted via NFS. On every node of the cluster the path to your HOME is the same. The filesystem space on HOME is limited by a quota! Due to the limited network performance, the HOME filesystem is not intended for fast I/O and for large files!
+
All user HOME directories for every compute node of the cluster are located on a shared RAID system. The compute nodes and login node (frontend) have the HOME directories mounted via NFS. On every node of the cluster the path to your HOME is the same. The filesystem space on HOME is limited by a quota! Due to the limited network performance, the HOME filesystem is not intended for fast I/O and for large files! To read or write even small files from many nodes (> 200) will
 +
cause trouble for all users. Applications should designate a single process to do the read and
 +
use broadcast mechanism (e.g. MPI_Bcast) to all nodes or use an parallel IO-mechanism like MPI-IO.
  
 
=== SCRATCH directories ===
 
=== SCRATCH directories ===

Revision as of 11:36, 5 May 2012

HOME Directories

All user HOME directories for every compute node of the cluster are located on a shared RAID system. The compute nodes and login node (frontend) have the HOME directories mounted via NFS. On every node of the cluster the path to your HOME is the same. The filesystem space on HOME is limited by a quota! Due to the limited network performance, the HOME filesystem is not intended for fast I/O and for large files! To read or write even small files from many nodes (> 200) will cause trouble for all users. Applications should designate a single process to do the read and use broadcast mechanism (e.g. MPI_Bcast) to all nodes or use an parallel IO-mechanism like MPI-IO.

SCRATCH directories

For large files and fast I/O, please use

  • lustre
    It's a fast distributed cluster filesystem using the high speed network infrastructure (Gemini). This filesystem is available on all nodes and on the frontend/login nodes.

You are responsible to obtain it from the system. To get access to this global scratch filesystems you have to use the [workspace mechanism]. Please notice, there is a maximum time limit for each workspace (30 days). After a workspace has exceeded the time limit, the workspace directory will be deleted.

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!

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