Difference between revisions of "Oldwiki.scinet.utoronto.ca:System Alerts"
m (→System Status) |
m (→System Status) |
||
| Line 35: | Line 35: | ||
<b>Tue Feb 28 10:02:45 EST 2017</b> It could take a few more hours. We still have a dozen or so users to go. Please check this page from time to time for updates. | <b>Tue Feb 28 10:02:45 EST 2017</b> It could take a few more hours. We still have a dozen or so users to go. Please check this page from time to time for updates. | ||
| − | <b>Mon 27 | + | <b>Mon Feb 27 2017 10:00:00 EST</b> The old scratch was 99% full. Given the current incident of scratch getting unmounted everywhere, we had little choice but to decide that it is time to initiate the transition to the new scratch file system at this point, instead of performing a roll-out approach that we had planned earlier. |
We estimate the transition to the new scratch will take roughly one day, but since we want all users' data on the old scratch system to be available in the new scratch (at the same logical location), the exact duration of the transition depends on the amount of new data to be transferred over. | We estimate the transition to the new scratch will take roughly one day, but since we want all users' data on the old scratch system to be available in the new scratch (at the same logical location), the exact duration of the transition depends on the amount of new data to be transferred over. | ||
| Line 45: | Line 45: | ||
The current scratch system issue and the scratch transition don't affect the BGQ or TCS anymore (although running jobs on TCS may have stopped this morning), because BGQ and TCS have their own separate scratch file systems. It also does not affect groups whose scratch space is on /scratch2. | The current scratch system issue and the scratch transition don't affect the BGQ or TCS anymore (although running jobs on TCS may have stopped this morning), because BGQ and TCS have their own separate scratch file systems. It also does not affect groups whose scratch space is on /scratch2. | ||
| − | <b>Mon 27 | + | <b>Mon Feb 27 2017 7:20:00 EST</b> Scratch file system is down. We are investigating. |
| − | <b>Wed 22 | + | <b>Wed Feb 22 2017 16:17:00 EST</b> Globus access to HPSS is currently not operational. We hope to have a resolution for this soon. |
<!-- [https://support.scinet.utoronto.ca/wiki/index.php/Previous_messages:] --> | <!-- [https://support.scinet.utoronto.ca/wiki/index.php/Previous_messages:] --> | ||
Revision as of 11:06, 28 February 2017
System Status
 GPC
|
 TCS
|
 Sandy
|
Gravity
|
BGQ
|
 File System
|
| P7
|
P8
|
KNL
|
Viz
|
HPSS
|
Tue Feb 28 10:02:45 EST 2017 It could take a few more hours. We still have a dozen or so users to go. Please check this page from time to time for updates.
Mon Feb 27 2017 10:00:00 EST The old scratch was 99% full. Given the current incident of scratch getting unmounted everywhere, we had little choice but to decide that it is time to initiate the transition to the new scratch file system at this point, instead of performing a roll-out approach that we had planned earlier.
We estimate the transition to the new scratch will take roughly one day, but since we want all users' data on the old scratch system to be available in the new scratch (at the same logical location), the exact duration of the transition depends on the amount of new data to be transferred over.
In the meantime, no jobs will start running on the GPC, Sandy, Gravity or P7.
In addition, $SCRATCH will not be accessible to users during the transition, but you can login to the login and devel nodes. $HOME is not affected.
The current scratch system issue and the scratch transition don't affect the BGQ or TCS anymore (although running jobs on TCS may have stopped this morning), because BGQ and TCS have their own separate scratch file systems. It also does not affect groups whose scratch space is on /scratch2.
Mon Feb 27 2017 7:20:00 EST Scratch file system is down. We are investigating.
Wed Feb 22 2017 16:17:00 EST Globus access to HPSS is currently not operational. We hope to have a resolution for this soon.