File-Level RAID-X Storage for Multiple Device Failure Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional data storage systems face challenges in efficiently reconstructing and restoring files when a RAID-X format is implemented at a volume level, as they fail to handle multiple device failures effectively, leading to data unavailability and access issues.

Innovation Solution

Implementing a RAID-X format at a file level within a plurality of storage devices, where a map is used to identify and reconstruct files with components stored across multiple devices, allowing for background reconstruction and continued data access even after exceeding the maximum limit of device failures for volume-level implementations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If RAID-X format is implemented at volume level, then data storage efficiency is improved, but the system cannot handle multiple device failures effectively

Engineering Contradiction:
Improvedata availabilityVSAvoidhandling multiple device failures
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the RAID-X implementation from volume level to file level. Each file is independently striped across storage devices with its own parity information, allowing individual file reconstruction even when multiple devices fail. This segmentation enables the system to handle multiple device failures by reconstructing only affected files rather than losing entire volumes.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimension of granularity by implementing RAID-X at the file level rather than volume level. This dimensional change allows independent error recovery for each file, transforming the system's ability to handle multiple failures from a binary state (volume loss) to a granular state (individual file recovery).

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If file reconstruction is performed after multiple device failures, then data integrity is improved, but system performance during reconstruction deteriorates

Engineering Contradiction:
Improvedata integrityVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements preliminary error detection by continuously monitoring storage device health and identifying failed components before they cause complete file loss. The system proactively initiates reconstruction operations for affected files, preventing data integrity issues before they occur and allowing controlled reconstruction during low-load periods.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent employs periodic background reconstruction operations that execute during low-system-activity periods. This periodic approach allows the system to maintain data integrity through continuous reconstruction while minimizing performance impact by scheduling operations during off-peak times rather than interrupting ongoing operations.

Inventive Principle:
Principle #19Periodic action

3Reliability

If file level RAID-X implementation is used, then reconstruction capability after multiple failures is improved, but system complexity increases

Engineering Contradiction:
Improvereconstruction capabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements self-service mechanisms where the storage system automatically detects device failures, identifies affected files, and initiates reconstruction operations without manual intervention. The system autonomously manages the complex coordination of reading surviving file components, computing parity information, and writing reconstructed data, thereby improving reconstruction capability while masking the underlying complexity from users.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces an intermediary file-level RAID management layer that sits between the storage devices and the file system. This intermediary handles the complex coordination of distributed file reconstruction by managing component identification, parity computation, and data assembly, thereby improving reconstruction capability while abstracting the complexity from both the storage devices and the file system.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Ease of operation

If background reconstruction operations are performed, then data access continuity is improved, but reconstruction time increases

Engineering Contradiction:
Improvedata access continuityVSAvoidreconstruction time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent implements continuous background reconstruction operations that proceed concurrently with normal data access operations. This continuity allows the system to maintain data access for unaffected files while simultaneously reconstructing damaged files in the background, ensuring operational continuity without interrupting user workflows and progressively reducing reconstruction time over multiple operation cycles.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS7793146B1Methods for storing data in a data storage system where a RAID-X format or formats are implemented at a file level
Publication Date: 2010.09.07 PANASAS INC
  • US7793146B1 patent drawing
  • US7793146B1 patent drawing
  • US7793146B1 patent drawing

AI summary

A data storage system where a RAID-X format is implemented at a file level includes storage devices, and one or more nodes that access files from the storage devices. N represents a maximum limit of failures beyond which reconstruction of a file stored using the file level implementation is not possible. A directory is encoded for each of a plurality of files, and a map is encoded that includes a list of storage devices where components of the directory associated with the map reside. The encoding of the directory is performed using a RAID-X format that can tolerate at least N+1 failures prior to being unable to reconstruct the directory.