Messages & Announcements

  • 2010-07-08:  Firefly /work space unavailable (again)
    Category:  System Failure

    Firefly's /work space is once again unavailable. Our storage system lost a storage blade and the system preemptively took the /work volume offline to prevent further issues.

    We are working with our storage vendor to resolve this issue.


    Firefly's /work space is once again unavailable. Our storage system lost a storage blade and the system preemptively took the /work volume offline to prevent further issues.

    We are working with our storage vendor to resolve this issue.

  • 2010-07-08:  Firefly /work space is available.
    Category:  System Failure

    This is related to the announcement that was sent out July 2, 2010 with the subject "Firefly Panasas" and the notification earlier today.

    The /work volume became available again shortly after I had sent out the offline notification.

    We are still working with our storage vendor to resolve this issue. A long term software patch should be available within the next week.


    This is related to the announcement that was sent out July 2, 2010 with the subject "Firefly Panasas" and the notification earlier today.

    The /work volume became available again shortly after I had sent out the offline notification.

    We are still working with our storage vendor to resolve this issue. A long term software patch should be available within the next week.

  • 2010-07-08:  Firefly /work space unavailable.
    Category:  System Failure


    This is related to the announcement that was sent out July 2, 2010 with the subject "Firefly Panasas".

    Firefly's /work space is temporarily unavailable. Our storage system lost a storage blade and the system preemptively took the /work volume offline to prevent further issues.

    We are working with our storage vendor to resolve this issue.

  • 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 hcc-support@unl.edu 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.

Pages