File System Snapshot Facility for OAS Metadata Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In object addressable storage systems, file system metadata can become corrupted, leading to incorrect storage location identification and data loss, especially due to power outages, system crashes, or concurrent file modifications, which existing protection methods like RAID and replication do not adequately address.
Innovation Solution
Implementing a snapshot facility that creates periodic snapshots of the file system, using techniques like copy-on-first-write or full copying, to maintain a consistent state and facilitate data recovery by storing metadata and content as it existed at a specific point in time, and optionally maintaining a list of object identifiers for lost content units.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If file system metadata is stored without protection mechanisms, then storage system complexity is reduced, but reliability deteriorates due to metadata corruption from power outages, system crashes, or concurrent modifications
Solution Approach 1:
The patent implements preliminary action by creating snapshots of the file system at specific points in time before potential corruption occurs. These snapshots capture the state of metadata and content, allowing recovery if corruption happens during subsequent operations. The snapshot mechanism proactively prepares protective copies rather than reacting to corruption after it occurs.
Solution Approach 2:
The patent applies the copying principle by creating duplicate copies of file system metadata and content through snapshots. These copies are stored separately from the primary file system structure, providing redundant information that can be used for recovery. The snapshot facility maintains these copies without requiring complex real-time protection mechanisms during normal operations.
2Reliability
If snapshots are created frequently to improve recovery capability, then data loss prevention improves, but storage space consumption increases
Solution Approach 1:
The patent implements partial action by creating snapshots that capture only the necessary portions of the file system state at given moments, rather than continuously copying all data. The snapshot facility selectively preserves metadata and content information needed for recovery, avoiding redundant storage of unchanged data blocks.
Solution Approach 2:
The patent applies parameter changes by adjusting the frequency and retention period of snapshots based on system needs. The snapshot mechanism can modify its behavior parameters such as snapshot interval, retention count, and scope to balance recovery capability with storage consumption, allowing optimization for different operational scenarios.
3Adaptability or versatility
If the file system uses object identifiers independent of physical location, then adaptability improves for OAS operations, but file system structure becomes more complex requiring translation layers
Solution Approach 1:
The patent implements the intermediary principle by introducing a translation layer between the OAS interface and the underlying file system. This intermediary component translates object identifiers from OAS operations into file system compatible forms, enabling the file system to support OAS functionality without fundamentally restructuring its core architecture. The translation layer handles the complexity of mapping between different identification schemes.
Solution Approach 2:
The patent applies segmentation by separating the OAS interface functionality from the core file system operations. The snapshot facility and translation mechanisms are implemented as distinct layers that can operate independently, allowing the file system to maintain its existing structure while adding OAS compatibility through modular components.
Data Source
AI summary
Aspects of the invention relate to creating a snapshot of a file system on an OAS system. A snapshot of a file system is an image of a file system at a particular point in time. A snapshot of a file system may be used to restore the file system to its state at the time of creation of the snapshot in, for example, situations where the file system has become corrupted.