Problem with /nobackupnfs2 filesystem server may cause data loss or corruption

Article ID: 498
Last updated: 26 Jan, 2016

Problem

Occasional data loss or corruption occurred in some output files that were sent to the /nobackupnfs2 filesystem.

Status: Resolved

We made a number of configuration changes to the /nobackupnfs2 filesystem to address the problem. Subsequently, the problem has not recurred.

Background

Due to a server issue, any data sent to the /nobackupnfs2 filesystem within a certain period (30 minutes to several hours) before the server hung/rebooted was being held in memory and not written to disk. After the server rebooted, the data in memory was lost, resulting in data loss or corruption.

Normally, data is continuously written to disk, so rebooting the server causes minimal if any data loss; writes to the filesystem are held during the reboot and the data can resume writing when the server is back up.

Contact Us

General User Assistance

Security

  • Report security issues 24x7x365
  • Toll-free: 1-877-NASA-SEC (1-877-627-2732)
  • E-mail: soc@nasa.gov

User Documentation

High-End Computing Capability (HECC) Portfolio Office

NASA High-End Computing Program

Tell Us About It

Our goal is furnish all the information you need to efficiently and effectively use the HECC resources needed for your NASA computational projects.

We welcome your input on features and topics that you would like to see included on this website.

Please send us email with your wish list and other feedback.