On July 17, 2025 from 7:00 AM - 10:00 PM the /project and /taiga file systems will not be available due to planned maintenance. Files in /projects or /taiga will not be accessible during the maintenance window.  As the maintenance day approaches it is recommended that jobs which do not need access to files in /projects or /taiga make use of a special reservation.  Jobs that are submitted to the special "no projects or taiga” reservation and do not specify  /projects or /taiga file systems as a Feature or constraint will be allowed to run during the /projects and /taiga file system maintenance. This reservation can run jobs before the reservation is active next week.

We recommend using the no_projects_taiga_requirements reservation in advance of the maintenance day. To submit new jobs to the special reservation, add the following

#SBATCH --reservation=no_projects_taiga_requirements

or use the command line option as in

$ sbatch --reservation= no_projects_taiga_requirements ...

 For jobs already submitted but not running and that might be scheduled to run during the maintenance day, use scontrol as follows to add the job to the reservation:

$ scontrol update reservation= no_projects_taiga_requirements job=JOBID

where JOBID is the slurm job id of the existing job. To verify the change use scontrol again as follows

$ scontrol show job JOBID | grep -i Reservation

and you should see

   Reservation= no_projects_taiga_requirements

 In general we recommend using Slurm's constraint and feature to indicate to the job scheduler which jobs depend on any file system including the projects or Taiga file system.

Jobs that have the projects or taiga file system as a Slurm Feature or constraint will be put on hold 2 days before the maintenance start time. See below for information on how to specify file systems as a job constraint for new jobs and as a Feature for already submitted jobs.