The scratch file system
From ALICE Documentation
The local scratch file system on
The scratch file system on
/scratchdata is a local file system on each node. It is intended as fast, temporary storage that can be used while running a job. The local scratch file system of a node can only be accessed when you run a job on that node.
There is no quota for the scratch file system, but use of it is eventually limited by the available storage space (see the Table in Summary of available file systems). Scratch disks are not backed up and are cleaned at the end of a job. This means that you have to move your data back to the shared scratch space at the end of your job or all your data will be lost.
Since the disks are local, read and write operations on
/scratchdata are much faster than on the home file system or the shared scratch file system. This makes it very suitable for I/O intensive operations.
How to best use local scratch
In general, the best way to use the local scratch file system on
/scratchdata is to copy your input files from your directory on
/data to the local scratch at the start of a job, create all temporary files needed by your job on the local scratch (assuming they don't need to be shared with other nodes) and copy all output files at the end of a job back to your
There are two things to note:
- On the node that your job is running on, a directory will be created for you upon the start of a job. The directory name is
SLURM_JOB_USERis your ALICE username and
SLURM_JOB_IDis the id of the job. You do not have to define these two variables yourself. They will be available for your to use in your job script.
- Do not forget to copy your results back to
/data! The local scratch space will be cleaned and the directory will be removed after your job finishes and your results will be lost if you forget this step.