$SCRATCH
`/scratch` file system is unresponsive
The issue has been resolved. We’ll keep an eye on things, but we’re confident this incident can be closed now.
The /scratch file system should be back up and running normally.
Processes that were stuck on I/O should have resumed automatically, but in case applications reported explicit errors, feel free to resubmit those jobs or restart those processes. And to reach out to srcc-support@stanford.edu if you have any questions.
We’re still investigating the issue, and are working on restoring access to /scratch as soon as possible.
The /scratch filesystem (which serves $SCRATCH and $GROUP_SCRATCH) is experiencing some issues. Symptoms include hanging commands and non-responsive access when trying to access anything under /scratch.
We’re currently investigating, and we’ll post updates as they become available