The maintenance on the Taiga servers that provide the /projects file system on Delta encountered an issue early last night. Delta staff are working with the vendors to resolve the issue and return the file system to service. Currently, no estimation is available for /projects return to service. We will provide updates as new information becomes available. The Delta system continues to run jobs that do not indicate a need for the /projects file system (see below).
The Delta projects (/projects) file system will be unavailable on March 14th from 8AM to 8PM for server-side maintenance.
The upgraded software will allow for the enforcement of quotas on the projects file system. We recommend that research teams that are over quota in /projects start to clean up and get back under quota.
Two days before the maintenance day, jobs already in the queue will be put on hold that have the projects file system as a slurm Feature or Constraint.
Jobs that do not require /projects or /taiga file systems as a Feature will be allowed to run. If your job requires files in /projects then be sure to add the appropriate constraint as shown below.
See below for information on how to specify file systems as a job Feature for already submitted jobs.
Please send questions to help@ncsa.illinois.edu and be sure to mention Delta in the subject or message body.
--Delta Project Office
To indicate that a job uses the /projects file system at job submission add the --constraint option to batch scripts:
#SBATCH --constraint="projects"
or add it to the command line:
$ sbatch --constraint="projects" ...
For an already submitted but not yet running job use:
$ scontrol update job=JOBID Features="projects"
replacing JOBID with the appropriate job id.