...
Scratch filesystems are a shared resource available for the convenience of all users. Therefore, files on these filesystems are subject to deletion after a certain lifespan as specified determined by the HPC policy committee. As of July 1 2016. Home account storage and purchased storage are not subject to this policy.
/localscratch
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.
/nfsscratch
On /nfsscratch, the allowed file lifespan is 60 days after first being written . On 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.
Home account storage and purchased storage are *not* subject to this policy.
| Note |
|---|
Duplicating Altering or duplicating files solely to circumvent the scratch cleanup process is against policy. Please make legitimate use of scratch filesystems, then move your intermediate and final results to stable storage in accordance with policy. |
Please contact hpc-sysadmins@iowa.uiowa.edu if you need with any questions or for assistance with this.
File Timestamps
Note that crtime is distinct from the other timestamps on a file:
Local or Shared Scratch?
- Multiple jobs might be running on your job's node. These jobs can compete for local storage I/O, causing contention independent of /nfsscratch. Only a job with exclusive access to a node can expect the full performance potential of the node's local storage.
- A parallel job running on multiple nodes typically shouldn't use filesystems local to any of its nodes. Even if you're writing your own MPI instead of using an off-the-shelf application, you can expect better performance if you collate results in memory via message passing and write your result to the shared filesystem. Consider local disk primarily as a structured alternative to swap.
- If your job places partial results on /localscratch but fails to handle them for any reason (logic error, eviction, crash, etc.), you won't have access to these anywhere else and they will be difficult to recover.
- As always, please test a few jobs if you are unsure.
File Timestamps
- modification time (mtime): This is the time the contents of the file were last modified, for example, by editing it. The modification time can be seen with
ls -l file
...
- access time (atime): This is the time the contents of the file were last accessed; for example, by viewing with 'less'. The access time can be seen with
ls -lu file
- creation time (crtime): This is the time the contents of the file were first written to the filesystem. This attribute is part of the underlying ZFS filesystem and is not accessible via NFS or standard Linux utilities.
It is possible for all All of these timestamps to can be different for a single file. Most file and archive utilities will maintain the first 3 timestamps, either by default or optionally. This includes using archive mode ('-a') with either 'cp' or 'rsync'. However, note that no utility can affect a file's crtime at all over NFS.
Local or Shared Scratch?
...
.