Each of these directories offers 5TB of storage space, accommodating the significant amount of temporary output that your programs may generate during execution.
Scratch Storage Information
Feature | Details |
---|---|
Directory | /scratch, /scratch2, or /scratch3 |
User Capacity | 5TB per storage directory |
Clean-up Policy | Files not accessed in the past 7 days are subject to system clean-up |
Usage |
|
To utilize scratch storage effectively, follow these example steps:
- Creates a directory for the job in the scratch directory
- Copies all files and directories from the source (/data/home/$USER/job1) to the scratch directory
- Changes the working directory to the scratch job directory and run your job
- Copies the results back to the home directory after the job completes
- Deletes the scratch directory to free up space after the job is done.
mkdir -p /scratch/$USER/job1
cp -a /data/home/$USER/job1/* /scratch/$USER/job1/
cd /scratch/$USER/job1 ./your_script_or_command_here
cp -a /scratch/$USER/job1/results/* /data/home/$USER/job1/results/
rm -rf /scratch/$USER/job1
Before running the example commands, please ensure that you update the folder directory paths to match your specific environment. The paths /data/home/$USER and /scratch/$USER are placeholders and should be replaced with the actual paths where your data is stored and where you want to perform your computations. For instance, if your data is located in /home/$USER/project1 and you want to use /scratch/$USER/project1 as your scratch directory, update the paths accordingly. Failing to modify these paths may result in errors or unintended file operations. Always double-check the paths to ensure they point to the correct locations.