Hierarchical File System Inode Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
As storage requirements grow, filesystems become increasingly prone to failures and corruptions due to software bugs or hardware issues, leading to longer recovery times and degraded availability and robustness, especially as more data and metadata need to be scanned for integrity verification and correction.
Innovation Solution
A method for storage management in hierarchical file systems that involves creating a structure with a top-file system and sub-file systems, where directories are tracked, and inode numbers are managed to ensure uniqueness across all sub-file systems, allowing for efficient redistribution of data and metadata to maintain balanced sub-file system sizes and prevent inode collisions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If filesystems grow to meet increasing storage requirements, then storage capacity increases, but the probability of failures and corruptions increases
Solution Approach 1:
The patent divides a large filesystem into multiple smaller sub-filesystems, each managed independently with its own inode space. This segmentation reduces the failure probability of the overall system because a failure in one sub-filesystem does not affect others, and recovery operations can be performed on smaller individual units rather than scanning the entire large filesystem.
2Quantity of substance
If more data and metadata are stored in the filesystem, then storage capacity increases, but recovery time increases
Solution Approach 1:
By segmenting the filesystem into sub-filesystems, the patent enables parallel recovery operations on multiple smaller units simultaneously. When a failure occurs, only the affected sub-filesystem needs to be scanned and recovered, rather than scanning the entire large filesystem, thus significantly reducing recovery time.
Solution Approach 2:
The patent pre-allocates unique inode number ranges to each sub-filesystem in advance. This preliminary assignment of unique inode spaces prevents inode collisions before they can occur, eliminating the need for time-consuming inode conflict detection and resolution during normal operations or recovery scenarios.
3Quantity of substance
If a hierarchical file system with multiple sub-file systems is created, then storage capacity and organization improve, but the complexity of managing unique inodes across all sub-file systems increases
Solution Approach 1:
The patent segments the global inode number space into distinct ranges allocated to each sub-filesystem. This segmentation simplifies management because each sub-filesystem operates with its own isolated inode namespace, eliminating the need for complex global inode allocation algorithms and conflict detection mechanisms across the entire hierarchical system.
Data Source
AI summary
One embodiment provides a method for storage management in a hierarchical file system that includes creating a structure for the hierarchical file system including a top-file system and sub-file systems that each include files and directories. Directories for the sub-file systems of the hierarchical file system are tracked. A request for creation of a unique directory in the hierarchical file system is received. Upon a request by a particular sub-file system for more inodes without any inodes available, inode numbers are revoked from at least one other sub-file system having unused inodes.