Storage Metadata Version Consistency and Reliability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing storage systems face challenges in ensuring metadata reliability and consistency, particularly in RAID-based systems, where failures can lead to inconsistencies in metadata versions across storage devices, affecting the ability to boot the system correctly.

Innovation Solution

A method is introduced to manage storage systems by reading multiple copies of metadata from a resource pool, selecting copies based on version information, and determining if the number of copies in the same version meets a predetermined condition (minimum copy count) to identify trusted metadata, ensuring that at least half of the storage devices provide consistent metadata for system reliability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple copies of metadata are stored across storage devices, then reliability is improved, but inconsistency in metadata versions may occur

Engineering Contradiction:
Improvemetadata reliabilityVSAvoidmetadata version consistency
Core Design Contradiction:
ReliabilityVSStability of the object's composition

Solution Approach 1:

The system performs preliminary actions by establishing version information tracking and minimum copy count verification before metadata operations. When reading metadata, the system first checks version consistency across copies and verifies that the number of copies meets the predetermined minimum threshold, preventing inconsistent metadata from being used before issues arise.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring the versions of metadata copies across storage devices. When version inconsistencies are detected or when the number of valid copies falls below the minimum threshold, the system generates feedback signals to trigger metadata reconstruction or system alerts, ensuring ongoing consistency.

Inventive Principle:
Principle #23Feedback

2Reliability

If metadata copies are distributed across more storage devices, then fault tolerance is improved, but system complexity increases

Engineering Contradiction:
Improvefault toleranceVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system manages complexity by dynamically adjusting parameters such as the minimum copy count threshold and version verification criteria based on system configuration and failure scenarios. This allows the system to optimize between fault tolerance and operational simplicity without requiring complex manual configuration.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system performs self-service by automatically detecting metadata version inconsistencies and copy count deficiencies, then autonomously triggering reconstruction processes or alerts without requiring complex external management systems. This reduces overall system complexity while maintaining high fault tolerance.

Inventive Principle:
Principle #25Self-service

3Measurement precision

If version checking is performed on all metadata copies, then metadata accuracy is improved, but processing time increases

Engineering Contradiction:
Improvemetadata version accuracyVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system applies partial action by performing version checking on a selective basis - specifically checking the number of copies against the minimum threshold and verifying version information only when necessary for system operations such as booting or metadata updates. This avoids exhaustive checking of all copies in all scenarios, reducing processing time while maintaining accuracy.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11429537B2Method, device, and computer program product for managing storage system
Publication Date: 2022.08.30 EMC IP HLDG CO LLC
  • US11429537B2 patent drawing
  • US11429537B2 patent drawing
  • US11429537B2 patent drawing

AI summary

Techniques involve managing a storage system. In accordance with the techniques, a plurality of copies of metadata of the storage system are read from a plurality of storage devices in a resource pool of the storage system. The resource pool includes a first number of storage devices, and the metadata describes configuration information of the storage system. A second number of copies are selected from the plurality of copies based on version information in the plurality of copies, where the second number of copies comprises the metadata in the same version. It is determined whether a relation between the first number and the second number satisfies a predetermined condition. The second number of copies are identified as trusted metadata based on determining the relation satisfies the predetermined condition. With the foregoing example implementation, the metadata in the storage system may be managed with higher reliability.