Data Corruption

About: Data Corruption is a research topic. Over the lifetime, 435 publications have been published within this topic receiving 6784 citations.

Apparatus, method and system for writing data to network accessible file system while minimizing risk of cache data loss/ data corruption

Abstract: Featured are methods for writing file systems write data operations to storage medium as well as system and program embodying such a methodology. According to one aspect, the method includes storing a file systems write data operation to a first temporary data store and mirroring the file systems write data operation in a second temporary data store. The method further includes deleting the mirrored file systems write data operation from the second temporary data store if it is successfully written from the first temporary data store to the storage medium and writing the mirrored file systems write data operation from the second temporary data store to the storage medium if it is not successfully written from the first temporary data store. In another aspect, the method includes storing the file systems write data operation in the first temporary data store of one server and mirroring it in the second temporary data store of another server. The method further includes monitoring the operational status of each server and writing the mirrored file systems write data operation from the second temporary data store of the other server to the storage medium when it is determined that one of the servers is not operational.

System and method to prevent data corruption due to split brain in shared data clusters

Abstract: A system and to prevent data corruption due to split brain in shared data clusters includes two or more nodes of a cluster, a shared storage device, and an update manager. The update manager may be configured to maintain a local persistent store corresponding to each node of the cluster. On receiving an update request directed to the shared storage device from a first node, the update manager may be configured to redirect the update to the local persistent store corresponding to the first node. The update manager may be further configured to verify a cluster membership status of the first node, and to transfer the contents of the update from the local persistent store to the shared storage device if the cluster membership verification succeeds.

Self-repairing operating system for computer entities

Abstract: A method of installing an operating system into a computer entity comprising at least one data storage device, a primary operating system and an emergency operating system, the method characterized by comprising the steps of: creating a copy of the primary operating system on an operating system back-up area of the data storage device of the computer entity; operating the computer entity using the emergency operating system; storing data of the computer entity on a user settings archive of the data storage device; replacing the primary operating system with the copy of the primary operating system; automatically checking for corrupted data on the user settings archive; restoring settings data of the computer entity from the user settings archive. In the event of a failure involving data corruption, application data may be deleted and recreated in a known good default state.

F-SEFI: A Fine-Grained Soft Error Fault Injection Tool for Profiling Application Vulnerability

Abstract: As the high performance computing (HPC) community continues to push towards exascale computing, resilience remains a serious challenge. With the expected decrease of both feature size and operating voltage, we expect a significant increase in hardware soft errors. HPC applications of today are only affected by soft errors to a small degree but we expect that this will become a more serious issue as HPC systems grow. We propose F-SEFI, a Fine-grained Soft Error Fault Injector, as a tool for profiling software robustness against soft errors. In this paper we utilize soft error injection to mimic the impact of errors on logic circuit behavior. Leveraging the open source virtual machine hypervisor QEMU, F-SEFI enables users to modify emulated machine instructions to introduce soft errors. F-SEFI can control what application, which sub-function, when and how to inject soft errors with different granularities, without interference to other applications that share the same environment. F-SEFI does this without requiring revisions to the application source code, compilers or operating systems. We discuss the design constraints for F-SEFI and the specifics of our implementation. We demonstrate use cases of F-SEFI on several benchmark applications to show how data corruption can propagate to incorrect results.

Method and apparatus for detecting and recovering from data corruption of a database via read prechecking and deferred maintenance of codewords

Abstract: A method of detecting and recovering from data corruption of a database is characterized by the step of protecting data of the database with codewords, one codeword for each region of the database; and verifying that a codeword matches associated data before the data is read from the database to prevent transaction-carried corruption. A deferred maintenance scheme is recommended for the codewords protecting the database such that the method of detecting and recovering from data corruption of a database may comprise the steps of protecting data of the database with codewords, one codeword for each region of the database; and asynchronously maintaining the codewords to improve concurrency of the database. Moreover, the database may be audited by using the codewords and noting them in a table and protecting regions of the database with latches. Once codeword values are computed and checked against noted values in memory, a flush can cause codewords from outstanding log records to be applied to the stored codeword table.