Service was fully restored at 10:45 PM EDT, and login functionality has returned to normal. No data loss occurred.

To prevent further impact, job submissions to clusters connected to Depot have been temporarily paused while the team works restore normal operation.

Impact: Users may experience job delays or failures when writing to the Data Depot.

Current Status: Our engineering team is actively addressing the capacity issue.

Next Update: We will provide an update once the service is restored or we have more information to share.

Due to the outage, some jobs on Gilbreth did not requeue automatically. Users should check the status of any jobs that were running early this morning and resubmit them if needed.

• Impact: Users are currently unable to access their home directories, and SSH connections or active terminal sessions may freeze or be denied.

• Current action: System administrators are performing a system reboot of the affected storage infrastructure to clear the error and restore file access.

Impact to you Attempts to read files that are on the affected storage may result in error messages

Our IT team is actively working with the vendor to restore service as quickly as possible. We will send an update as soon as more information is available.

We appreciate your patience and understanding as we work to restore Gilbreth service.

We will provide updates as the situation develops and once service is fully restored.

We appreciate your patience and understanding.

System monitoring has identified an issue where heavy job activity was overloading the Data Depot filesystem used by the clusters and Globus.

You may see the following impacts:

• Globus transfers to and from Depot collections may fail, stall, or run much more slowly than usual.
• Globus logins may be slow or occasionally fail when accessing Depot endpoints.
• Jobs on RCAC clusters that read from or write to Depot may experience slow file access, delayed directory listings, or timeouts.

Our engineers are investigating the high load from a large number of concurrent jobs and are working to reduce the impact on Depot, Globus, and cluster workloads. Existing jobs will continue to run, but any that are heavily Depot‑I/O‑bound may run more slowly or see I/O errors until performance improves. We will provide another update by 5:00PM EST or sooner if the issue is resolved.

Our team is actively investigating and will post updates as soon as more information is available or 4pm EST. Thank you for your patience and understanding!

We will provide an update by 2:00PM EST today.

We will provide an update by 2:00 PM EST or sooner.

We will provide an update by 9pm.

We will provide an update by 11 AM.

The Data Depot file system has returned to full service and scheduling has resumed on all clusters.

The Data Depot storage system began experience issues starting around 9am EDT this morning. Engineers are currently diagnosing the issue and are working to identify a fix. Job scheduling has been paused while this issue is being addressed.

We will provide an update by 12pm (noon).

Data Depot functionality has been restored.

The Data Depot file system began experiencing issues with writes around 2:30pm EDT. The data migration process currently ongoing from Data Depot 2 to Data Depot 3 ran into an unexpected problem. Engineers have identified the problem and are correcting it. Users may have seen "no space left on device" for approximately 30 minutes. Job scheduling has been paused while this issue is being addressed.

We will provide an update by 5 PM.

Our engineers are working on the fix, and will keep this updated.

The problem has been fixed at 5 pm.

No ETA at this time. We will update as soon as possible or by 5:00pm EST.