Metadata Resiliency via Redundant Copying Across Storage Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional storage systems face inefficiencies in managing metadata resiliency during storage device failures, leading to inconsistencies and data loss due to inadequate redundancy and quorum policies.

Innovation Solution

Implementing an I/O processing module that redundantly copies metadata across different storage devices and manages sequence numbers to ensure metadata validity and redundancy, allowing the system to tolerate multiple storage device failures by maintaining a quorum policy and generating additional copies as needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If metadata is stored on a single storage device, then storage device complexity is reduced, but metadata resiliency deteriorates when storage devices fail

Engineering Contradiction:
Improvestorage device managementVSAvoidmetadata resiliency
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system creates redundant copies of metadata across multiple storage devices. When metadata is updated, copies are propagated to other storage devices in the array, ensuring that metadata remains accessible even if some storage devices fail. This copying mechanism directly addresses the contradiction by sacrificing some device management complexity to achieve metadata resiliency.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system proactively creates and maintains metadata copies on multiple storage devices before failures occur. The quorum policy is established in advance, determining the minimum number of readable copies needed to access metadata. This preliminary action ensures that when storage devices fail, metadata resiliency is already in place without requiring complex real-time management during failures.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If metadata copies are maintained across multiple storage devices, then metadata resiliency is improved, but storage system complexity increases

Engineering Contradiction:
Improvemetadata resiliencyVSAvoidmetadata copy management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system employs self-service mechanisms where storage devices automatically participate in metadata replication and recovery without requiring complex external management. When a storage device joins the array or when failures occur, the system automatically redistributes metadata copies to maintain the quorum policy, reducing the need for manual intervention and simplifying overall system management.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses feedback mechanisms to monitor the state of metadata copies across storage devices. The quorum policy provides feedback on whether sufficient readable copies exist, and the system automatically adjusts by creating or recovering copies as needed. This feedback loop simplifies management by providing clear state information and automated response mechanisms.

Inventive Principle:
Principle #23Feedback

3Manufacturing precision

If quorum policy requires multiple readable metadata copies, then data integrity is improved, but I/O operation time increases due to coordination overhead

Engineering Contradiction:
Improvedata integrityVSAvoidI/O operation time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-establishing the quorum of readable metadata copies before I/O operations occur. Metadata is proactively replicated across sufficient storage devices in advance, so when I/O operations need to access metadata, the required copies are already available. This eliminates the need for time-consuming coordination and search operations during actual I/O transactions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system applies local quality by ensuring that each storage device maintains local copies of metadata according to the quorum policy. This distributed local storage of metadata copies allows I/O operations to access metadata from nearby available storage devices without requiring centralized coordination, thereby reducing I/O operation time while maintaining data integrity through the quorum requirement.

Inventive Principle:
Principle #3Local quality

4Quantity of substance

If storage devices are added or removed from the array, then storage capacity is improved, but metadata consistency becomes difficult to maintain

Engineering Contradiction:
Improvestorage capacityVSAvoidmetadata consistency
Core Design Contradiction:
Quantity of substanceVSStability of the object's composition

Solution Approach 1:

The system employs dynamic mechanisms that automatically adapt to changes in storage device composition. When storage devices are added or removed, the system dynamically redistributes metadata copies to maintain the quorum policy and ensure consistency. This dynamic response allows storage capacity to change while automatically preserving metadata consistency without requiring manual reconfiguration or complex stabilization procedures.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10467107B1Maintaining metadata resiliency among storage device failures
Publication Date: 2019.11.05 PURE STORAGE INC
  • US10467107B1 patent drawing
  • US10467107B1 patent drawing
  • US10467107B1 patent drawing

AI summary

Maintaining metadata consistency among storage devices failures, which includes: for each of a plurality of datasets: writing, on different storage devices of a respective write group, a respective plurality of copies of a respective dataset corresponding to a respective identifier, where at least one copy of the respective dataset remains readable after less than a threshold number of storage device failures within the write group; and responsive to recovering from a system interruption: generating a catalog of valid datasets based on one or more identifiers stored among readable storage devices of the respective write groups.