Skip to content

Commit

Permalink
Merge branch 'main' into alcf-haritha-patch-2
Browse files Browse the repository at this point in the history
  • Loading branch information
@felker
felker committed Sep 9, 2024
2 parents ae94d3d + edcdcaf commit b966bb8
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/data-management/filesystem-and-storage/file-systems.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,13 +7,13 @@ For more information on the Lustre file system, here is a document on Lustre Fil

For information on the AI Testbed storage systems, refer to the AI Testbed storage page: [https://argonne-lcf.github.io/ai-testbed-userdocs/common/storage/](https://argonne-lcf.github.io/ai-testbed-userdocs/common/storage/)

Our HPC systems also share a Lustre home file system, called swift-home. The home file system is mounted as /home, and should generally be used for small files and any binaries to be run on Polaris. The performance of this file system is reasonable, but using it for intensive I/O from the compute nodes is discouraged because I/O from the compute nodes uses the project data file systems, which are fast parallel systems and have far more storage space and greater I/O performance than the home directory space.
Our HPC systems also share a Lustre home file system, called agile-home. The home file system is mounted as /home, and should generally be used for small files and any binaries to be run on Polaris. The performance of this file system is reasonable, but using it for intensive I/O from the compute nodes is discouraged because I/O from the compute nodes uses the project data file systems, which are fast parallel systems and have far more storage space and greater I/O performance than the home directory space.

The swift-home file system is regularly backed up to tape. The data file system is not backed up. It is the user’s responsibility to ensure that copies of any critical data on the data file system have either been archived to tape or stored elsewhere.
The agile-home file system is regularly backed up to tape. The data file system is not backed up. It is the user’s responsibility to ensure that copies of any critical data on the data file system have either been archived to tape or stored elsewhere.

| Name | Accessible From | Type | Path | Production | Backed-up | Usage |
|--------------------------------------|----------|--------|---------------------------------------------------------------------------------------|-----------------------------------------------|-----------|------------------------------------------------------------------------|
| swift-home | Polaris | Lustre | /home or /lus/swift/home | Yes | Yes | General use |
| agile-home | Polaris | Lustre | /home or /lus/agile/home | Yes | Yes | General use |
| Grand | Polaris | Lustre | /grand or /lus/grand/projects | Yes | No | Intensive job output, large files |
| Eagle | Polaris | Lustre | /eagle or /lus/eagle/projects | Yes | No | Community sharing via Globus; <br /> Intensive job output, large files |
| Node SSD <br /><br /> (Compute node only) | Polaris | xfs | /local/scratch (Polaris) | Yes | No | Local node scratch during run |
Expand Down

0 comments on commit b966bb8

Please sign in to comment.