Logical View Storage Management via Shared Inode Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional snapshot copy facilities in data storage systems face challenges in creating versions of a namespace, leading to high storage and memory usage due to the need to create duplicate copies of files, limiting the number of namespace views and snapshot copies that can be managed.
Innovation Solution
The technique involves creating a logical view with a namespace inode that virtualizes the inodes of files, allowing sharing between the namespace and snapshot copies, using a delegated reference counting mechanism to manage access and storage, thereby reducing the need for duplicate copies and improving storage and memory utilization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional snapshot copy facilities create duplicate copies of files for each namespace view, then data integrity and availability are ensured, but storage requirements and memory usage increase significantly
Solution Approach 1:
The patent merges the inode structures across different namespace views and snapshot copies by implementing a shared inode mechanism. Instead of creating separate duplicate inode structures for each view, the system uses a single shared inode that is referenced by multiple namespace views and snapshot copies, thereby reducing storage requirements while maintaining data integrity and availability.
Solution Approach 2:
The patent introduces a mapping structure that acts as an intermediary between the shared inode and different namespace views. This mapping structure allows multiple namespace views to access the same underlying inode without requiring duplicate copies, while maintaining logical separation and data integrity for each view.
2Adaptability or versatility
If duplicate copies of files are created for each namespace view, then access control and data isolation are maintained, but the number of manageable namespace views and snapshot copies is limited
Solution Approach 1:
The patent merges inode management across multiple namespace views by implementing a shared inode mechanism with reference counting. This allows the system to track and manage multiple views through a single inode structure, increasing the number of manageable namespace views while reducing the complexity of storage management through unified inode handling.
3Reliability
If conventional snapshot facilities create separate inode structures for each version, then data isolation between versions is ensured, but memory usage increases
Solution Approach 1:
The patent merges inode structures across different versions by implementing a shared inode mechanism. Instead of creating separate inode structures for each version, the system shares a common inode structure that is referenced by multiple versions, thereby reducing memory usage while maintaining data isolation through version-specific mapping structures.
Data Source
AI summary
A method is used in managing logical views of storage. A logical view is created. The logical view includes a set of storage objects. A mapping object for the logical view is created. The mapping object manages access to the set of objects of the logical view. A snapshot copy of the logical view is created. The snapshot copy of the logical view shares a subset of the set of storage objects with the logical view. A version of the mapping object manages access to the snapshot copy.