Hierarchical File System Properties Inheritance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing file systems lack a robust method for maintaining persistent and hierarchical naming of file systems and associating properties, leading to temporary name bindings and per-file system property management, which is inefficient and lacks inheritance of attributes.
Innovation Solution
A hierarchical data structure is used to maintain file system names and properties, where each file system inherits attributes from its parent nodes, allowing for a method to determine attribute values by tracing the path from the file system to the storage pool, ensuring persistent naming and attribute inheritance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Duration of action of stationary object
If temporary name binding is used for file systems, then the file system can be mounted and accessed at a specified location, but the name binding ceases to exist once the file system is unmounted, lacking persistence
Solution Approach 1:
The patent creates a persistent symbolic link in the hierarchical data structure before the file system is unmounted. This preliminary action ensures that when the file system is remounted or accessed later, the name binding is already in place, eliminating the need for temporary bindings and ensuring continuous accessibility.
Solution Approach 2:
The patent creates a symbolic link that copies the reference to the file system's real path in the hierarchical data structure. This copy persists independently of the file system's mount state, allowing the name binding to survive unmount operations and be restored automatically when needed.
2Adaptability or versatility
If properties are associated with file systems on a per-file system basis, then each file system can have its own properties, but the management becomes inefficient and lacks inheritance of attributes
Solution Approach 1:
The patent segments the property management system into hierarchical levels: pool-level default properties and file system-level specific properties. This segmentation allows properties to be defined once at the pool level and automatically inherited by multiple file systems, reducing management complexity while maintaining customization capability where needed.
Solution Approach 2:
The patent adds a hierarchical dimension to property management by organizing properties in a tree structure with pool-level and file system-level nodes. This dimensional change enables properties to flow downward through the hierarchy, allowing efficient inheritance while preserving the ability to override specific properties at lower levels.
3Adaptability or versatility
If manual per-file system property associations are used, then each file system can have customized properties, but the process is time-consuming and lacks scalability
Solution Approach 1:
The patent implements self-service property inheritance where file systems automatically receive default properties from their parent pool nodes in the hierarchical data structure. This eliminates the need for manual property association, as the system automatically services the property inheritance requirement, greatly improving productivity while maintaining customization options.
Solution Approach 2:
The patent merges the property definition and inheritance process into a unified hierarchical structure. By combining pool-level default property definition with automatic file system-level inheritance, the system eliminates the separate manual association process, improving efficiency while preserving adaptability through selective overrides.
Data Source
AI summary
A storage pool, that includes a hierarchical data structure, wherein the hierarchical data structure comprises a plurality of nodes, wherein one of the plurality of nodes corresponds to the file system, and the file system, wherein the file system is associated with a value corresponding to an attribute, wherein the value is determined using the hierarchical data structure.