Owens
Rolling Reboot
We will have rolling reboots of all three clusters (Owens, Ruby, and Pitzer) including login and compute nodes, starting from 9:30 AM Wednesday, June 05, 2019. The rolling reboots will address the caching problems on the file systems. The rolling reboots won't affect any running jobs, but users may experience longer queue wait time than usual on the cluster.
We apologize for any inconvenience this may cause you. Please contact oschelp@osc.edu if you have any questions.
PROBLEM WITH GPFS FILESYSTEM ON 06/04/2019
We fixed the problem with both project and scratch filesystem and the service has been restored.
Xalt on Owens
Date:
Tuesday, May 21, 2019 - 6:15pm
System(s):
We added xalt module in the default environment.
xalt tracks the software usage information. If you have any issues with, please contact oschelp@osc.edu.
PROBLEM WITH GPFS FILESYSTEM SINCE 05/18/2019
We fixed the problem with both project and scratch filesystem. For more information, see this link: https://bit.ly/2WPuo2i
Batch Limit Rules
Memory Limit:
A small portion of the total physical memory on each node is reserved for distributed processes. The actual physical memory available to user jobs is tabulated below.
CHANGE OF DEFAULT MATLAB VERSION
OSC is changing the default version of MATLAB on all clusters from R2018a to R2018b effective Friday, April 26th. Several bugs exist in R2018a that have been addressed in R2018b. This change may cause some MATLAB jobs to fail. To review release notes for R2018b, please visit this link: https://bit.ly/2GvGjeM
To continue using R2018a in your jobs, you need to load the module "matlab/r2018a". If you need any assistance at all, please contact OSCHelp@osc.edu
SYSTEM DOWNTIME MAY 21, 2019
A downtime for all HPC systems is scheduled from 7 a.m. to 5 p.m., Tuesday, May 21, 2019. The downtime will affect the Pitzer, Ruby and Owens Clusters, web portals and HPC file servers. Login services, including my.osc.edu, access to storage and the HyperWorks license server hosted by OSC will not be available during this time. In preparation for the downtime, the batch scheduler will begin holding jobs that cannot be completed before 7 a.m., May 21, 2019. Jobs that are not started will be held until after the downtime and then started once the system is returned to production status.