| 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 |
|---|
| icon | false |
|---|
| title | Migration: 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.
...
| Column |
|---|
| Tip |
|---|
| title | Use 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. |
| Warning |
|---|
| Files which have not been accessed for the purge period of 30 21 days will be deleted automatically and WILL BE LOST. See Filesystem Policies.
(Note that this was changed since Monday 10th of June 2024, removing the previous rule of 1-month)
|
| Warning |
|---|
| title | Do not Never 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. See Filesystem Policies.
As mentioned above, users should incorporate regular file movement from /scratch into Acacia for long-term storage. |
|
...
Leaving files to be removed by the 3021-day purge policy places an unnecessary load on the filesystem as the system is scanned for these files, and causes less capacity to be available for other users.
...
| Column |
|---|
Table 1. Pawsey filesystems: capacity, file limit and duration | Filesystem | Capacity Limit | File Limit | Duration |
|---|
/home | 1 GB per user | 10k files per user | Active project allocation | /software | 256 GB per project | 100k files per user | Active project allocation | /scratch | 1 PB per project | 1M files per user | 30 21 days from last modification (see Filesystem Policies) |
|
The default group membership for files and directories that are created in /home is the user's primary group, which is the same as their user ID. Files and directories that are created in any of the Lustre filesystems are associated by default with the user's project ID.
...