Object Storage Volume Dynamic Metadata Allocation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional filesystems face inefficiencies in large-scale storage systems due to namespace collisions and limited metadata storage capabilities, which can lead to reduced usable space for object data as metadata grows unpredictably, necessitating overprovisioning and limiting flexibility in metadata expansion.

Innovation Solution

An object storage device dynamically allocates logical block addresses within a single logical block address space for both metadata and data, allowing for flexible reallocation to optimize storage usage, with higher performance tiers for metadata and lower performance tiers for data, enabling scalable metadata storage without predefined constraints.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If traditional filesystems allocate fixed metadata storage, then metadata can be stored, but usable space for object data is reduced due to overprovisioning and namespace collisions

Engineering Contradiction:
Improveusable storage spaceVSAvoidmetadata expansion flexibility
Core Design Contradiction:
Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic allocation of logical block addresses for metadata storage, allowing the metadata range to expand or contract based on actual needs rather than fixed pre-allocation. The controller dynamically adjusts the metadata range within the single logical block address space, enabling flexible metadata expansion without overprovisioning and maximizing usable storage space for object data.

Inventive Principle:
Principle #15Dynamics

2Ease of operation

If separate storage volumes are used for metadata and data, then organization is improved, but device complexity and namespace collisions increase

Engineering Contradiction:
Improvemetadata and data organizationVSAvoidstorage volume management
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent merges metadata storage and object data storage into a single logical block address space while maintaining logical separation through dynamic range allocation. The controller manages both metadata and data within one volume, eliminating namespace collisions between separate volumes while preserving organizational benefits through controlled range assignments. This unified approach reduces device complexity by eliminating the need to manage multiple separate storage volumes.

Inventive Principle:
Principle #5Merging (Combining)

3Speed

If fixed performance tiers are assigned to metadata and data, then performance is optimized, but storage utilization flexibility is reduced

Engineering Contradiction:
Improvemetadata access latencyVSAvoidstorage allocation flexibility
Core Design Contradiction:
SpeedVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic tier allocation where performance tiers are not fixed to specific metadata or data ranges but are dynamically assigned based on actual performance needs and storage conditions. The controller can reallocate tiers within the single logical block address space to optimize both metadata access latency and storage utilization flexibility, allowing high-performance regions to be dynamically assigned to whichever range (metadata or data) requires them most at any given time.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11829288B2Mapping of object data and metadata in an object storage volume
Publication Date: 2023.11.28 SEAGATE TECH LLC
  • US11829288B2 patent drawing
  • US11829288B2 patent drawing
  • US11829288B2 patent drawing

AI summary

A volume for object storage encompasses a single logical block address space and the first range of logical block addresses being within the single logical block address space. A first and second range of logical block addresses are initially allocated within the single logical block address space of the volume for storing respective object metadata and object data. One or both of the first and second ranges of logical block addresses are reallocated to increase storage utilized by one of the object metadata and the object data.