Versions Compared

Old Version 28

changes.mady.by.user Alexis Espinosa

Saved on

compared with

New Version 29

changes.mady.by.user Alexis Espinosa

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Excerpt

There are multiple filesystems mounted to each of Pawsey's supercomputers. Each of these filesystems are designed for particular use cases. This page provides a detailed description of these filesystems.

...

Apart from /home, all are Lustre distributed filesystems. Lustre is an open-source, high performance parallel file system optimised for high throughput. 

Column


Note
iconfalse
titleMigration: Filesystems

While Pawsey is migrating to Setonix, there are existing filesystems still in use by Garrawarla.

  • The existing /astro filesystem, which will be replaced by the new /scratch filesystem on Setonix.


...

The /software  filesystem is a Lustre file system with much higher throughput than /home. It is intended for software installations and Slurm batch script templates. Each project has an associated directory on the filesystem whose path is /software/projects/<project>. Within a project directory, each project member has his or her own directory whose full path, /software/projects/<project>/<username>, is contained in the MYSOFTWARE environment variable.

...

/scratch is a Lustre filesystem and its location is available in the environment variable $MYSCRATCH.

$ echo $MYSCRATCH


Column


Tip
titleUse Acacia to store your data

The scratch file system is not intended for long-term storage, is not backed up and is purged on a regular basis. If you wish to retain files, move them to the Acacia object storage.

Column


Warning
titleWarning:

Files which have not been accessed for the purge period of 30 days will be deleted automatically and WILL BE LOST. See Filesystem Policies.


Warning
titleDo not use the `touch` command to avoid purge

The use of the touch command to avoid purging generates overloading of the metadata servers of the /scratch filesystem. Remember that /scratch is shared among all users. Therefore, users should respect the best practices to avoid overloading of metadata servers at all times. Overloading of the metadata servers dramatically degrade performance affecting all users at the same time. Pawsey reserves the right to revoke access to users that do not respect this best practice.

As mentioned above, users should incorporate regular file movement from /scratch into Acacia for long-term storage.


The /scratch filesystem has the highest performance of the available filesystems, and allows jobs to temporarily use large amounts of storage while running. However, to maintain high performance for all users, there are limits of 2PB per project and 2 million files per user.

...