You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: excl-support/backup.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,15 +31,16 @@ We can also help diagnose the cause of large storage use by providing a breakdow
31
31
In addition to shared network storage, each system has a local `/scratch`
32
32
directory. The size will vary from system to system, and some systems may
33
33
have `/scratch2` in addition. A working space can be created with
34
-
`mkdir /srcatch$USER` if one is not already present.
34
+
`mkdir /scratch$USER` if one is not already present.
35
35
This storage location is good for caching files on local host storage,
36
36
for speeding up tasks which are storage IO bound, and performing tasks
37
-
which can’t be done on NFS storage (for example, Apptainer and
38
-
embedded Linux builds).
39
-
If you require more scratch storage than is available, or if you have
40
-
any difficulty using `/scratch` including a missing /scratch or /scratch2 directory, contact
41
-
[excl-help@ornl.gov](mailto:excl-help@ornl.gov) as on newer systems there is often additional
42
-
storage available that has not been allocated. Since there is no purging policy, please clean up after you no longer need the scratch space.
37
+
which fail on NFS storage (for example, Apptainer and embedded Linux builds).
38
+
If you require more scratch storage than is available contact
39
+
[excl-help@ornl.gov](mailto:excl-help@ornl.gov) as on newer systems there is
40
+
often additional storage available that has not been allocated.
41
+
Similarly contact us if there is no /scratch or /scratch2 directory.
42
+
Since there is (currently) no purging policy, please clean up after you
43
+
no longer need your scratch space.
43
44
44
45
{% hint style="danger" %}
45
46
`/scratch/` is not shared between nodes, not stored in raid, and not backed up in any way. However, this storage does not have any automatic purging policy (unlike `/tmp/`), so the files should persist as long as the storage doesn’t fill up and the drives don’t fail.
0 commit comments