File System Inconsistency Detection and Reconstruction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
File system consistency check (FSCK) tools fail to detect and repair inconsistencies in user data, especially when namespace correlations are lost or primal metadata is corrupted, leading to orphaned files and performance overheads from replicated metadata.
Innovation Solution
A system that creates a database for metadata associated with hierarchical organization directories and policy/configuration data files, allowing for consistency checks and reconstruction, using inode IDs and extended attributes to recover orphaned objects and ensure file system integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If FSCK tools use traditional consistency check methods, then they can detect some file system errors, but they fail to detect and repair inconsistencies in user data when namespace correlations are lost or primal metadata is corrupted
Solution Approach 1:
The patent creates a database containing copies of metadata associated with hierarchical organization directories and policy/configuration data files. This metadata database serves as a backup representation that can be used when the original primal metadata is corrupted or lost, enabling the consistency check tool to recover and validate file system structures even when traditional metadata is unavailable
Solution Approach 2:
The patent introduces a metadata database as an intermediary layer between the file system structures and the consistency check tool. This database acts as a mediator that stores essential metadata information, allowing the tool to perform consistency checks without directly relying on potentially corrupted primal metadata in the file system
2Reliability
If FSCK tools create replicas of primal metadata to overcome corruption problems, then they can perform consistency checks, but this results in performance overhead and storage overheads
Solution Approach 1:
The patent extracts only the essential metadata information needed for consistency checking into a separate database, rather than creating complete replicas of the primal metadata. This selective extraction reduces the amount of data that needs to be stored and processed, thereby reducing both storage overhead and performance overhead while maintaining the ability to perform consistency checks
3Ease of repair
If FSCK tools place orphaned files in an orphaned objects directory, then they can recover files whose original names cannot be determined, but they cannot restore files to the right name and hierarchy in the namespace
Solution Approach 1:
The patent stores copies of metadata including hierarchical organization information in the metadata database. This metadata contains information about the original names, parent directories, and hierarchical relationships of files and directories. When orphaned objects are detected, the tool uses this copied metadata to restore them to their correct names and hierarchical positions in the namespace
Data Source
AI summary
In one example, a system is described in which a storage device, communicatively coupled to a processor, includes an inconsistency detection and reconstruction tool. The inconsistency detection and reconstruction tool may create a database including metadata associated with hierarchical organization directories and policy and configuration data files in a file system. Further, the inconsistency detection and reconstruction tool may perform consistency check of one or more of the hierarchical organization directories, the policy and configuration data files and the metadata to detect inconsistencies. Furthermore, the inconsistency detection and reconstruction tool may reconstruct one or more of the hierarchical organization directories, the policy and configuration data files and the metadata based on the outcome of the consistency check.