13.1. Central Scratch Space

A total of 67Gb is currently available for central scratch space. This space is shared amongst all users. Each user has a directory within the central scratch space allocated to them. This directory is automounted as

    /scratch/bohrg/<username>

13.2. Scratch Space Local to Compute Nodes

All compute nodes have scratch space available to users on a local/internal disk. I/O to local scratch space should be faster than to central scratch space.

The amount of local scratch space available varies from node to node, but a minimum of 8.2Gb should be available on all nodes:

Dominion

On Dominion 8.2Gb of scratch space is available on each node. This is currently mounted on /scratch_local

Bohrg

On Bohrg, some machines have one internal disk while others have two, so that the amount of local scratch space available varies considerably. Roughly speaking, nodes making up the "Big Mem queue" (more accurately, parallel environment) have 19Gb, while the other nodes have 14Gb.

13.3. Rules of Usage

...

13.4. Links from Home Directories to Central Scratch Space

...

13.5. Tidy-Up Scripts

On some machines hosted by Manchester Computing scratch space is regularly "tidied up", e.g., files created more that a month ago are automatically deleted. At present (2005 Apr 19) there is no such automated deletion. Should scratch space become short this automation might be introduced.

13.6. Quotas

There are currently no scratch space quotas in operation. If space becomes short quotas will be introduced.

13.7. Backups

Scratch space is not backed up. Do not store any files in scratch space which you need to keep or cannot easily reproduce (e.g., from a re-run of a job).