Versions Compared

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.

...

The software filesystem is intended for software installations and Slurm batch script templates. Each project has an associated directory, /software/projects/<project>, with a quota of 256 GB per project. (More can be allocated upon justified request.) Within the project directory, each project member has a subdirectory, /software/projects/<project>/<username>, with a limit of 100,000 individual files per user.

...

All members of a project have read and write access to the /software/projects/<project> directory, so it can be used for sharing software installations and batch script templates within a project. Your allocation of space on /software exists for the duration of the project and is not subject to any automatic purging.

...

Column


Warning

If you encounter a write error, compiler error, or file transfer error on the /scratch or /software filesystems, this is likely because the files are counting against your personal group quota rather than your project's group quota.



Column


test
Tip

You should proactively and regularly monitor both file count and quota usage across the filesystems. This practice will reduce your likelihood of hitting the quota limits; whenever this happens, no files can be written until usage is brought back below quota.

As regards the /home filesystem, regularly check for and clean unneeded files, which may be generated by software as temporary or cache files. These are often stored in hidden directories (their name starts with a dot).


File permissions are also important to consider. Here are the default permissions of a file named myscript.sh that was created in a user's home directory:

...