...
On /localscratch, the allowed file lifespan is 30 days after the file was last accessed, and a file's age is the time elapsed since its access timestamp ("atime"). An automated cleanup process will run periodically on each node to delete files whose atime has reached the maximum lifespan. It is also expected that large amounts of data put on /localscratch are cleaned up at the end of a job. Otherwise, the node become unavailable. A node left in this condition will have /localscratch clean entirely, irrespective of time stamps, to make the node available again.
/nfsscratch
On /nfsscratch, the allowed file lifespan is 60 days after first being written to an /nfsscratch filesystem, and a file's age is the time elapsed since its creation timestamp ("crtime") which is tracked on the fileserver. An automated cleanup process will run periodically on the server to delete files whose crtime has reached the maximum lifespan.
...