Gordon User Guide: Storage Overview
SSD Scratch Space
Both the native (non-vSMP) compute nodes and the vSMP nodes on Gordon have access to fast flash storage. Most of the native compute nodes mount a single 300 GB SSD (280 GB usable space), but four of the native nodes, labeled with the "bigflash" property, have access to a 4.4 TB SSD filesystem. The vSMP nodes have access to one or more RAID 0 devices each built from sixteen 300 GB SSDs (4.4 TB usable space).
The latency to the SSDs is several orders of magnitude lower than that for spinning disk (<100 microseconds vs. milliseconds) making them ideal for user-level check pointing and applications that need fast random I/O to large scratch files. Users can access the SSDs only during job execution under the following directories:
Regular native compute nodes:
Note that the regular compute nodes have 280GB of usable space in the scratch SSD location. For jobs needing larger scratch space, the options are “bigflash” compute nodes and the vSMP nodes.
Bigflash native compute nodes (maximum of 4 nodes):
Additionally, users will have to change the PBS node request line:
#PBS –l nodes=number_of_nodes:ppn=16:native:bigflash
If more than one bigflash node is needed (we have 4 available) for the run, the following line also needs to be added since all four nodes are not on the same switch:
#PBS –v Catalina_maxhops=2
/scratch1/$USER/$PBS_JOBID (16-way and larger) /scratch2/$USER/$PBS_JOBID (32-way and larger)
For the vSMP nodes, /scratch is a symbolic link to /scratch1 and is provided to maintain a consistent interface to the SSDs across all SDSC resources that contain flash drives (Gordon and Trestles).
The directories are purged immediately after the job terminates, therefore any desired files should be copied to either the home or parallel file system before the end of the job.
Parallel Lustre File System
SDSC provides several Lustre-based parallel file systems. These include a shared Projects Storage area that is mounted on both Gordon and Trestles plus separate scratch file systems. Collectively known as Data Oasis, these file systems are accessed through 64 Object Storage Servers (OSSs) and will have an eventual capacity of 4 PB.
Lustre Project Space
SDSC Projects Storage has 400 TB of capacity and is available to all allocated users of Trestles and Gordon. It is accessible at:
Where <allocation> is your 6-character allocation name, found by running show_accounts. The default allocation is 500 GB of Project Storage to be shared among all users of a project. Projects that require more than 500 GB of Project Storage must request additional space by sending an email to email@example.com. This e-mail from the project PI should provide a justification in 500 words or fewer that includes:
- the amount of storage being requested;
- how the storage will be used; and
- how this augments other non-SDSC storage resources available to the project.
SDSC staff will review the projects storage requests and a decision will be made within 5 business days.
Project Storage is single copy, not backed up, not purged, and users should ensure that critical data are duplicated elsewhere. Space is provided on a per-project basis and is available for the duration of the associated compute allocation period. Data will be retained for 3 months beyond the end of the project, by which time data must be migrated elsewhere.
Lustre Scratch Space
The Gordon Scratch space has a capacity of 1.6 PB and is currently configured as follows.
Users cannot write directly to the /oasis/scratch/$USER directory and must instead write to one of the two subdirectories listed above.
The former is created at the start of a job and should be used for applications that require a shared scratch space or need more storage than can be provided by the flash drives. As users can only access the scratch space after the job starts, executables and other input data can be copied here from the user's home directory. Unlike SSD scratch storage, the data stored in Lustre scratch is not purged immediately after job completion. Instead, users will have time after the job completes to copy back data they wish to retain to their projects directories, home directories, or to their home institution.
The latter is intended for medium-term storage, but is subject to purge with a minimum of five days notice if it begins to approach capacity.
Note that both directories ($PBS_JOBID and temp_project) are part of the same file system and therefore served by the same set of OSSs. User jobs can read or write to either location with the same performance. To avoid the overhead of unnecessary data movement, read directly from temp_project rather than copying to the $PBS_JOBID directory. Similarly, files that should be retained after completion of a job should be written directly to temp_project.
Home File System
After logging in, users are placed in their home directory, /home, also referenced by the environment variable $HOME. The home directory is limited in space and should be used only for source code storage. Production runs should not make use of the home file system, as it is not set up for high performance throughput. Users should keep usage on $HOME under 100GB. Backups are currently being stored on a rolling 8-week period. In case of file corruption/data loss, please contact us at firstname.lastname@example.org to retrieve the requested files.