Scratch: Difference between revisions
(Linkify) |
No edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== Scratch (/scratch) == |
|||
<code>[[Machine List#corn-syrup|corn-syrup]]</code> hosts <code>/scratch</code>, which is a 1TB free-for-all filesystem. The general rule for using <code>/scratch</code> is not to be a dick. Don't gobble up all the space. Users are encouraged to use it for good, and especially for datasets or intermediate code in large compiles that would otherwise exceed their normal quota. |
<code>[[Machine List#corn-syrup|corn-syrup]]</code> hosts <code>/scratch</code>, which is a 1TB free-for-all filesystem. The general rule for using <code>/scratch</code> is not to be a dick. Don't gobble up all the space. Users are encouraged to use it for good, and especially for datasets or intermediate code in large compiles that would otherwise exceed their normal quota. |
||
There is no expectation of data permanence in <code>/scratch</code>; data could be cleared out at any time by [[syscom]]. |
There is no expectation of data permanence in <code>/scratch</code>; data could be cleared out at any time by [[syscom]]. That being said, notice should be given unless there are special circumstances that warrant otherwise. |
||
<code>/scratch</code> is exported over NFS, but it will be fastest if accessed from <code>corn-syrup</code>, and it's recommended that any computations or compilations be done on that machine. |
<code>/scratch</code> is exported over NFS, but it will be fastest if accessed from <code>corn-syrup</code>, and it's recommended that any computations or compilations be done on that machine. |
||
== HFCS Scratch (/scratch-hfcs) == |
|||
[[Machine List#high-fructose-corn-syrup|high-fructose-corn-syrup]] has a local scratch mounted at <code>/scratch-hfcs</code>. The same rules as <code>/scratch</code> apply for anything stored here. |
|||
Latest revision as of 22:02, 11 April 2018
Scratch (/scratch)
corn-syrup hosts /scratch, which is a 1TB free-for-all filesystem. The general rule for using /scratch is not to be a dick. Don't gobble up all the space. Users are encouraged to use it for good, and especially for datasets or intermediate code in large compiles that would otherwise exceed their normal quota.
There is no expectation of data permanence in /scratch; data could be cleared out at any time by syscom. That being said, notice should be given unless there are special circumstances that warrant otherwise.
/scratch is exported over NFS, but it will be fastest if accessed from corn-syrup, and it's recommended that any computations or compilations be done on that machine.
HFCS Scratch (/scratch-hfcs)
high-fructose-corn-syrup has a local scratch mounted at /scratch-hfcs. The same rules as /scratch apply for anything stored here.