Object Storage Backed File System Namespace Translation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing file systems struggle to efficiently interact 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 introduced, which creates and manages namespace objects and inode objects to bridge the gap between hierarchical and flat namespaces, utilizing 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

VSEngineering Contradiction Analysis

1Adaptability or versatility

If object storage is used to provide scalability and flexibility, then storage capacity and accessibility are improved, but namespace consistency and hierarchical structure are lost

Engineering Contradiction:

Improvestorage scalabilityVSAvoidnamespace consistency

Core Design Contradiction:

Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent introduces a file system interface layer that acts as an intermediary between traditional file system applications and object storage. This layer translates hierarchical file system commands into flat namespace object storage operations, preserving the hierarchical namespace view for applications while leveraging object storage's scalability. The intermediary maintains namespace consistency by managing the translation between hierarchical and flat namespaces without requiring applications to be aware of the underlying object storage structure.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the file system functionality into distinct components: a traditional file system interface layer and an object storage backend layer. The file system layer handles hierarchical namespace operations, while the object storage layer provides scalable flat namespace storage. This segmentation allows each layer to operate independently with its own optimization, resolving the contradiction between hierarchical consistency and flat namespace scalability.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If traditional file system commands are used to interact with object storage, then application compatibility is improved, but command execution efficiency deteriorates

Engineering Contradiction:

Improveapplication compatibilityVSAvoidcommand execution efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent replaces the mechanical translation process of file system commands with optimized direct object storage operations. Instead of translating every traditional file system command into multiple object storage requests, the system uses direct object storage APIs and operations that are natively optimized for object storage. This substitution maintains application compatibility through the file system interface while dramatically improving execution efficiency by eliminating unnecessary translation overhead.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Ease of operation

If hierarchical namespace structure is maintained for file system compatibility, then application interaction is simplified, but storage efficiency and scalability are reduced

Engineering Contradiction:

Improveapplication interactionVSAvoidstorage efficiency

Core Design Contradiction:

Ease of operationVSProductivity

Solution Approach 1:

The patent resolves this contradiction by operating in two dimensional spaces simultaneously: the hierarchical namespace dimension for application interaction and the flat namespace dimension for storage efficiency. Applications continue to interact with the familiar hierarchical structure through the file system interface, while the underlying object storage operates in the flat namespace dimension for optimal efficiency and scalability. This dimensional separation allows both requirements to be satisfied without compromise.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS11334540B2Namespace hierarchy preservation with multiple object storage objects

Publication Date: 2022.05.17 NETAPP INC

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.