File System Segregating Data and Metadata Subspaces
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data storage systems face performance impairments due to the interspersing of user data with metadata, leading to inefficient resource utilization and access issues, as metadata is accessed more frequently than user data.
Innovation Solution
The file system is divided into multiple subspaces: a data subspace for user data, an inode subspace for inodes, and a metadata block subspace for indirect blocks and directory structures, allowing for segregated storage and flexible allocation units, with the option to provision storage based on tiered storage policies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If user data and metadata are interspersed in the same storage space, then the file system structure is simple, but storage resource utilization is inefficient and access performance deteriorates
Solution Approach 1:
The file system divides the addressable storage space into multiple distinct subspaces: a data subspace for user data, an inode subspace for inode metadata, and an MDB subspace for other metadata. This segmentation allows independent management and optimization of each subspace, improving storage resource utilization and access efficiency while maintaining a manageable file system structure through systematic organization.
2Ease of operation
If user data and metadata are stored together, then storage allocation is uniform, but access efficiency decreases due to frequent metadata access
Solution Approach 1:
The patent segments the storage space into data subspace and metadata subspaces (inode and MDB), allowing differentiated allocation strategies. The data subspace can use larger allocation units optimized for user data, while metadata subspaces use smaller allocation units suited for frequent access patterns, thereby improving overall access efficiency without complicating allocation management.
Solution Approach 2:
Different allocation unit sizes are applied to different subspaces based on their specific access characteristics. The data subspace employs larger allocation units appropriate for user data storage, while metadata subspaces use smaller allocation units optimized for frequent read/write operations, ensuring each subspace has the optimal allocation characteristics for its function.
3Ease of manufacture
If the file system uses a unified storage structure, then implementation is straightforward, but adaptability to different storage tiers and future metadata types is limited
Solution Approach 1:
By dividing the file system into distinct subspaces (data, inode, MDB), the patent creates a modular structure that can independently associate with different storage tiers. Each subspace can be configured with appropriate storage policies and tier associations, providing adaptability to various storage configurations while maintaining implementation simplicity through consistent subspace management procedures.
Solution Approach 2:
The subspace architecture provides a universal framework that can accommodate different storage tiers and future metadata types. The same subspace structure can be applied regardless of the underlying storage technology or metadata requirements, enabling the file system to adapt to evolving storage technologies and additional metadata needs without fundamental redesign.
Data Source
AI summary
A technique for managing a file system includes dividing the addressable space of a file system into multiple subspaces: a data subspace for user data; an inode subspace for inodes describing the user data; and an MDB (metadata block) subspace for indirect blocks and/or directory structures pertaining to the user data. In response to storage requests to write user files to the file system, the file system stores user data of the files in the data subspace, stores inodes pertaining to the user files in the inode subspace, and stores indirect blocks and/or directories in the MDB subspace.