Object Storage Backed File System Namespace Translation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing file systems struggle to seamlessly integrate with object storage solutions, as they are designed for hierarchical namespaces, while object storage employs a flat namespace, leading to inefficiencies in handling file system commands and maintaining namespace consistency across geographically distributed environments.
Innovation Solution
An object storage backed file system (OSFS) is implemented, which creates and manages namespace objects and inode objects to bridge the gap between hierarchical and flat namespaces, using a file system cache mechanism to transform file system commands into object storage operations, ensuring efficient execution and consistency across clients.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If object storage is used to provide geographically distributed storage, then scalability and flexibility are improved, but compatibility with existing file system applications and namespace consistency deteriorate
Solution Approach 1:
The patent introduces a file system gateway as an intermediary component that sits between file system applications and object storage. This gateway translates file system commands into object storage operations, bridging the compatibility gap between hierarchical file system interfaces and flat object storage namespaces while maintaining namespace consistency across geographically distributed environments
2Productivity
If direct object storage access is used, then scalability is improved, but ease of operation for file system applications deteriorates
Solution Approach 1:
The patent creates a virtual copy of the file system interface layer that operates over object storage. This virtual file system layer replicates familiar file system semantics and operations, allowing applications to interact with object storage through standard file system commands without directly accessing the underlying object storage API, thereby maintaining ease of operation while leveraging object storage scalability
3Adaptability or versatility
If hierarchical namespace is implemented over flat object storage, then compatibility with existing applications is improved, but device complexity increases
Solution Approach 1:
The patent segments the namespace management functionality into distinct components within the file system gateway. The hierarchical namespace is divided into manageable segments that map to underlying object storage operations, with each segment handling specific aspects of namespace translation independently. This modular segmentation reduces overall system complexity while maintaining application compatibility
Data Source
AI summary
To leverage the attributes of object storage for applications/systems created to interface with a network files system, an object storage backed file system can accept the defined file system commands from the applications/systems and transform the file system commands into requests that target object storage. The file system is “backed” by object storage because attributes and content of file system entities are stored in objects. For instance, content data and metadata of a file are stored in objects in object storage. This object storage backed file system can be considered a bridge between a client perceived hierarchical file system namespace and a flat namespace of an object storage.