Write-Layer Metadata Cache for Shared Application File Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing information handling systems face challenges in preserving user-specific modifications when rename or delete operations are performed on shared application layers, leading to loss of file data and poor user experience.
Innovation Solution
Implementing a write-layer metadata cache that simulates rename and delete operations by creating virtual links and tracking metadata flags to redirect file operations, ensuring that user-specific data is preserved and accessed correctly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If rename or delete operations are performed on shared application layers, then file operations can be executed, but user-specific modifications are lost and file data is lost
Solution Approach 1:
The patent introduces a metadata cache as an intermediary layer between the shared application layer and the user's view of the file system. This metadata cache stores information about user-specific modifications and intercepts rename/delete operations, preventing direct modification of the shared layer while maintaining the illusion of successful operations to the user. The metadata cache acts as a buffer that decouples the user's file operations from the actual shared layer, preserving both operational ease and data integrity.
2Reliability
If user-specific modifications are preserved on read-only layers, then data protection is improved, but file operation complexity increases
Solution Approach 1:
The patent creates virtual copies of file operations in the metadata cache rather than performing actual operations on the shared layer. When a user renames or deletes a file, the system creates a corresponding entry in the metadata cache that simulates the operation's effect. This copying approach allows the system to maintain complex protection mechanisms while presenting simple, familiar file operations to the user, as the metadata cache handles the complexity of reconciling user actions with the read-only nature of the shared layer.
3Reliability
If metadata cache is implemented to track file operations, then file protection is improved, but system resource usage increases
Solution Approach 1:
The patent implements the metadata cache with local quality by storing only the specific information needed to protect against rename and delete operations, rather than maintaining complete file system state. The metadata cache focuses selectively on tracking user-specific modifications and operation history relevant to protection, rather than caching all possible file attributes. This selective approach reduces memory consumption while maintaining effective protection against the specific operations that threaten data integrity.
Data Source
AI summary
Files and folders on a read-only shared layer may be protected by using a read-write layer. File system level hooks are added to capture and simulate the rename and delete operation that would otherwise corrupt or destroy files and folders on a read-only layer. Each read-write layer has an associated file system metadata cache that gives an overview of the data contained by the layer. Relevant metadata is added for the metadata entry associated with a file or folder subjected to a rename or delete operation so as to track the file system operations associated with the file or folder. One or more metadata flags may be used to assist in tracking the file system operations.