Messages & Announcements

  • 2010-07-07:  PrairieFire Maintenance Concluded
    Category:  Maintenance

    Maintenance and reorganization of the /home filesystem on PrairieFire is complete. The system is up and open to all users.

    The /home filesystem has been replicated and reorganized. Two Sun NFS fileservers now share the load of distributing /home. Further, Merritt now has its own standalone filesystem. Quotas of 100 GB have been implemented per research group. /home is only to be used for files that are necessary for functioning on PrairieFire, such as code, difficult to recreate input files, and so on. A best-effort backup is maintained for /home, but this is not an archiving service. The backup is only a protection against catastrophic loss.

    /work should be used for running jobs, temporary storage of large output files, and so on. Unlike /home, if /work fills up, HCC staff will delete existing files as needed to maintain system functionality. Users should never store precious data on /work. Files will be deleted according to age (oldest first) and largest usage amount (per group). All users are asked to remove files from /work as soon as possible.

    Further dedicated storage may be purchased in collaboration with HCC. Please contact David Swanson for details.

  • 2010-07-02:  PrairieFire Status
    Category:  Maintenance

    PrairieFire filesystem maintenance nearing completion. System may remain down until Tuesday (following the 4th holiday break). Please contact if you need access to files before then. Firefly and Merritt remain up and available.

    PrairieFire's home filesystem was previously a single large NFS server from SUN, and has failed repeatedly over the last month. It appears no data has been lost. Several steps are nearing completion. First, the /home filesystem for Merritt, previously also served from this box, has been moved to other hardware. Moving forward, Merritt and PrairieFire are decoupled. Next, another smaller filesystems that was served by the same box has been moved to other hardware. Finally, a complete replica of /home for PrairieFire nears completion on a similar server. This will allow us to balance the load over both, as well as providing us with a ready failover system. A third similar box will be optimized for performance and tested after PrairieFire is back online.

  • 2010-06-30:  Service restored to Merritt.
    Category:  General Announcement

    Service has been restored to Merritt. Prairiefire remains inaccessible for maintenance.

    Merritt's /home filesystem has been migrated to a different storage system, and it is now available to run jobs. Users are encouraged to check that their files are intact. Prairiefire remains down to reorganize its /home fileservers.

  • 2010-07-01:  PrairieFire and Merritt unplanned down time
    Category:  System Failure

    PrairieFire and Merritt are in an unplanned down time due to filesystem issues until further notice.

    The home filesystems for Prairiefire and Merritt are not responsive. These systems will remain down until a suitable solution is found. Firefly remains up, and we will work with you if you need access to resources not readily available there. We will announce further details and time frames here as they become available.

    ***** added 7/1/10 *******
    Maintenance of the home filesystem for PrairieFire is requiring extended down time. We are moving to a strategy that uses multiple NFS servers, which requires movement and replication of data. This process is progressing without trouble, but is admittedly very time consuming. PrairieFire will remain off-line at least until the end of this week.

  • 2010-06-23:  Prairiefire Rebooted
    Category:  System Failure

    PRAIRIEFIRE: Rebooted

    Kernel tweeked on NFS home fileserver, rebooted to read new params, will watch to see performance ongoing...