File Virtualization Unit Decoupling from Open Source File System Upgrades
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The frequent and irregular version upgrades of open source software (OSS) for file systems necessitate frequent updates of the file virtualization function, leading to significant labor and effort, disrupting the provision of this function in storage systems.
Innovation Solution
A file storage system architecture that includes a first file system, a processor, state management information, and a file virtualization unit, allowing the system to manage file operations and virtualization independently of OSS version upgrades by using a second storage system and performing IO Hook processing to monitor and manage file operations across both systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the file system uses open source software (OSS) with frequent version upgrades, then the system can benefit from continuous improvements and new features, but the file virtualization function requires frequent updates leading to enormous labor and effort
Solution Approach 1:
The system divides the file management functionality into two independent segments: the file system (which uses OSS and undergoes version upgrades) and the file virtualization function (which maintains stable interfaces). This segmentation allows the file system to evolve independently while the virtualization layer remains unchanged, eliminating the need for frequent updates to the virtualization function.
Solution Approach 2:
The patent introduces an intermediary layer between the file system and the file virtualization function. This intermediary handles the interaction between the two components, allowing the virtualization function to communicate with the file system through stable, version-independent interfaces. The intermediary absorbs the impact of OSS version changes, preventing them from propagating to the virtualization function.
2Reliability
If the file virtualization function is tightly coupled with the file system version, then the function can be optimized for each version, but the system requires continuous updates and maintenance effort
Solution Approach 1:
The file virtualization function is designed with universal interfaces that work across multiple OSS versions without modification. The virtualization function performs multiple roles (migration, stubbing, restoration) through a single stable implementation, eliminating the need for version-specific optimizations and reducing update time.
3Ease of manufacture
If the system maintains stable file virtualization function across OSS versions, then update effort is reduced, but the system must abstract away version-specific optimizations
Solution Approach 1:
The system implements dynamic adaptation at the file system level while maintaining static interfaces at the virtualization level. The file system can dynamically optimize operations for each OSS version internally, while the virtualization function maintains a stable, version-independent interface. This dynamic adaptation occurs within the file system layer without affecting the virtualization function's productivity.
Data Source
AI summary
A file storage system configured to use a second storage system includes a first file system provided to an application, a first storage system in which a file is stored by the first file system, a processor, state management information storing a state of the file, a state information management unit that manages the state management information, and a file virtualization unit that manages files stored in the first storage system and the second storage system. The processor performs a calling process of the first file system based on an operation request of the file from the application. The first file system processes the operation request of the file. The state information management unit performs a state management information update process of the file based on input information with respect to the first file system related to the operation request, or an operation content.