RAID Storage Write Path Selection for Resiliency and Performance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

RAID storage systems face performance degradation and data loss risks when operating in degraded mode due to insufficient spare capacity and resiliency, leading to inefficiencies in handling user I/O write requests.

Innovation Solution

The implementation of a method within a storage control system that selectively chooses between performing degraded writes or writes to spare capacity based on the RAID array's operational mode, determining the availability of spare capacity and the level of resiliency to ensure fault tolerance and optimize performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If degraded writes are used to handle user I/O write requests in degraded mode, then I/O performance is maintained, but data resiliency and fault tolerance are reduced

Engineering Contradiction:
ImproveI/O performanceVSAvoiddata resiliency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system dynamically adjusts write operation behavior based on real-time monitoring of spare capacity availability and resiliency levels. The storage control system transitions between degraded writes and writes to spare capacity depending on current system state, making the write path adaptive rather than static.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes operational parameters (write destination selection) based on monitored conditions. When spare capacity becomes available or resiliency thresholds are met, the system transitions from degraded write mode to full write mode, effectively changing the system's operational parameters in response to state changes.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If writes are performed to spare capacity, then data resiliency is improved, but I/O performance is degraded due to additional write operations

Engineering Contradiction:
Improvedata resiliencyVSAvoidI/O performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by proactively writing data to spare capacity when it becomes available, before actual failures occur. This preliminary reconstruction of data to spare capacity ensures resiliency is maintained without impacting user I/O performance during normal operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses idle or available spare capacity to service its own resiliency needs automatically. When spare capacity is available, the system autonomously performs writes to maintain fault tolerance without requiring additional user I/O operations, effectively making the resiliency mechanism self-service rather than user-burdened.

Inventive Principle:
Principle #25Self-service

3Reliability

If spare capacity is allocated for rebuilding missing data, then fault tolerance is enhanced, but available capacity for user I/O operations is reduced

Engineering Contradiction:
Improvefault toleranceVSAvoidavailable capacity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

Spare capacity serves multiple functions: it acts as both a buffer for failed device reconstruction and as available storage for user I/O operations when not needed for rebuilding. The system dynamically allocates and deallocates spare capacity between these two competing uses based on current system needs, maximizing its utility across different operational states.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11301162B2Balancing resiliency and performance by selective use of degraded writes and spare capacity in storage systems
Publication Date: 2022.04.12 EMC IP HLDG CO LLC
  • US11301162B2 patent drawing
  • US11301162B2 patent drawing
  • US11301162B2 patent drawing

AI summary

Techniques are provided for processing user input/output (I/O) write requests in a fault-tolerant data storage system (e.g., a RAID storage system) by selecting between performing a degraded write operation or a write operation to spare capacity, when the fault-tolerant data storage system is operating in a degraded mode. A method includes receiving a user I/O write request comprising data to be written to a RAID array operating in a degraded mode, and determining whether spare capacity has been allocated for rebuilding missing data of an inaccessible storage device of the RAID array and whether a missing data block, which is associated with I/O write request, has been rebuilt to the spare capacity. A degraded write operation is performed without using the spare capacity, when the missing data block, which is associated with the data of the I/O write request, has not been rebuilt to the allocated spare capacity.