FAS Research Computing - Historial de avisos

Sistema en mantenimiento

Status page for the Harvard FAS Research Computing cluster and other resources.

Cluster Utilization (VPN and FASRC login required): Cannon | FASSE


Please scroll down to see details on any Incidents or maintenance notices.
Monthly maintenance occurs on the first Monday of the month (except holidays).

GETTING HELP
Documentation: https://docs.rc.fas.harvard.edu | Account Portal https://portal.rc.fas.harvard.edu
Email: rchelp@rc.fas.harvard.edu | Support Hours


The colors shown in the bars below were chosen to increase visibility for color-blind visitors.
For higher contrast, switch to light mode at the bottom of this page if the background is dark and colors are muted.

En mantenimiento

SLURM Scheduler - Cannon - En mantenimiento

Cannon Compute Cluster (Holyoke) - En mantenimiento

Boston Compute Nodes - En mantenimiento

GPU nodes (Holyoke) - En mantenimiento

seas_compute - En mantenimiento

En mantenimiento

SLURM Scheduler - FASSE - En mantenimiento

FASSE Compute Cluster (Holyoke) - En mantenimiento

En mantenimiento

Kempner Cluster CPU - En mantenimiento

Kempner Cluster GPU - En mantenimiento

Operativo

FASSE login nodes - Operativo

Operativo

Cannon Open OnDemand - Operativo

FASSE Open OnDemand - Operativo

Interrupción parcial

Netscratch (Global Scratch) - Operativo

Home Directory Storage - Boston - Operativo

Tape - (Tier 3) - Operativo

Holylabs - Operativo

Isilon Storage Holyoke (Tier 1) - Operativo

Holystore01 (Tier 0) - Operativo

HolyLFS04 (Tier 0) - Operativo

HolyLFS05 (Tier 0) - Operativo

HolyLFS06 (Tier 0) - Operativo

Holyoke Tier 2 NFS - Interrupción parcial

Holyoke Specialty Storage - Operativo

holECS - Operativo

Isilon Storage Boston (Tier 1) - Operativo

BosLFS02 (Tier 0) - Operativo

Boston Tier 2 NFS - Operativo

CEPH Storage Boston (Tier 2) - Operativo

Boston Specialty Storage - Operativo

bosECS - Operativo

Samba Cluster - Operativo

Globus Data Transfer - Operativo

Historial de avisos

Ver estado actual

jul 2022

JUL21
NESE tape (Tier 3) hardware maintenance/install
CompletadoMantenimiento12 horas
  • Completado
    julio 21, 2022 a 22:00UTC
    Completado
    julio 21, 2022 a 22:00UTC

    Maintenance has completed successfully

  • En curso
    julio 21, 2022 a 10:00UTC
    En curso
    julio 21, 2022 a 10:00UTC

    Maintenance is now in progress

  • Planificado
    julio 21, 2022 a 10:00UTC
    Planificado
    julio 21, 2022 a 10:00UTC

    Our tier 3 tape system is part of and run by NESE (the NorthEast Storage Exchange).

    We have been informed that they will be installing additional tape drives to the system on July 21st and this will require a whole day downtime to accomplish. Tier 3 tape archives will not be available to our users on that date.

holylfs02 performance issues
Resuelto815 horas 14 minutos
  • Resuelto
    UTC
    Resuelto

    The unrepairable volume on holylfs02 is isolated to two labs and they have been informed of next steps. This issue does not affect other areas on holylfs02, so we are closing this incident.

  • Actualizar
    UTC
    Actualizar

    Recently we noticed an uptick in bad blocks on a RAID6 disk volume that is part of the entire filesystem. Generally speaking, the operating system will vector these out so no data is written there. During this period, we had to replace a number of drives due to failures; they are part of RAID 6 multi-disk set with dual parity and will rebuild with minimal impact on performance.

    What we believe happened is that, during the rebuild process, bad data was copied to the replacement disks and the filesystem got corrupted. One of the staff ran a read-only, non-destructive repair on the volume in question and noted quite a few errors.

    So far, we have 1) contacted the vendor (who gave us a command to clear additional bad blocks)
    2) NOT run the actual repair command to "fix" the filesystem (which would delete data) 3) contacted the vendor to see if they had any partners that might be able to assist. We are planning to meet with one of those partners early next week, but are not confident they will have a solution. At this point (and depending on how that meeting goes), the next step would be to run the repair, note the extent of loss, and attempt to get the volume remounted.

    Updates to follow when we have more information.

    Note that these shelves are covered under warranty support for another year. We see no need at present to replace the 3PB allocation with new hardware (this is planned to take place Q3-4 FY23)

  • Identificado
    UTC
    Identificado

    Users may experience issues connecting to holylfs02, or slow samba performance.

    This is due to a hardware issue with holylfs02, and we have opened a ticket with the vendor. Updates to follow.

    No ETA.

jun 2022

may 2022

Slurm security patch causing node unavailability
ResueltoRendimiento degradado2 horas 30 minutos
  • Resuelto
    UTC
    Resuelto

    The scheduler and node states appear to be stable. Thank you for your patience and understanding.

    Please note that the intermittent deadlock issue is still not resolved, but we are actively monitoring that and intervening as necessary until we receive a solution.

  • Supervisando
    UTC
    Supervisando

    The patch has been deployed and the scheduler restarted. Paused jobs are resuming.

    Any jobs which did not start or were stuck may have been flushed. So please check any pending jobs you might have had.

    Related doc: https://docs.rc.fas.harvard.edu/kb/running-jobs/.

  • Identificado
    UTC
    Identificado

    We have tested the patch on our test cluster before releasing. We are now proceeding to deploy to the cluster. Thanks for your patience.

    UPDATE: jobs suspended, scheduler down for patching, nodes are updating.

  • Investigando
    UTC
    Investigando

    The Slurm emergency security patch introduced a bug which is causing many of our nodes to be set to 'not responding'. The vendor has already identified the issue and issued another patch.

    We are deploying this patch after testing. Jobs will be paused and the scheduler and cluster will be unavailable while deploying the patch. Watch here for updates.

Anterior

may 2022 a jul 2022

Siguiente