Disk Repair Strategy for Mirrored Files

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for repairing disk failures in mirrored file systems either leave data unprotected for a long time or incur high computational costs, as they either immediately recreate the entire disk or wait for administrative repair, respectively.

Innovation Solution

A method to determine a threshold value for transient disk failures, allowing for efficient repair strategies that minimize data unavailability by recreating only stale data blocks if the disk is repaired within the threshold time, or recreating the entire disk if not, using metadata to track current and stale data blocks and implementing disk resync operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system immediately recreates the entire disk content after a failure, then data redundancy is restored quickly, but computational cost increases significantly and data blocks remain unprotected for a long period

Engineering Contradiction:
Improvedata redundancyVSAvoidcomputational cost
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Instead of completely recreating the entire disk content, the system performs partial action by only resynchronizing stale data blocks that were written after the failure occurred. This selective approach restores necessary redundancy while avoiding the excessive computational cost of full recreation.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system performs preliminary action by tracking which data blocks are stale (written after failure) and preparing to resynchronize only those blocks. This preliminary identification of affected blocks enables efficient partial recovery without unnecessary full disk recreation.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If the system waits for administrative repair of the failing disk, then computational cost is reduced, but data blocks remain unprotected and data availability decreases

Engineering Contradiction:
Improvecomputational costVSAvoiddata unavailability time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs self-service by automatically detecting disk failures, identifying stale data blocks, and initiating resynchronization operations without requiring administrative intervention. This enables the system to recover autonomously while minimizing data unavailability time.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses feedback mechanisms to monitor disk status and track which data blocks are stale. This feedback information enables the system to make informed decisions about when and what to resynchronize, optimizing both computational cost and data availability.

Inventive Principle:
Principle #23Feedback

3Productivity

If the system resynchronizes only stale data blocks, then computational cost is reduced, but data blocks remain unprotected while waiting for repair confirmation

Engineering Contradiction:
Improvecomputational costVSAvoiddata protection
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system applies dynamics by adjusting its behavior based on real-time conditions. It dynamically decides whether to resynchronize stale blocks immediately or wait for administrative repair confirmation, optimizing the balance between computational cost and data protection based on the specific failure scenario.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS7565575B2Selecting optimal repair strategy for mirrored files
Publication Date: 2009.07.21 ORACLE INT CORP
  • US7565575B2 patent drawing
  • US7565575B2 patent drawing
  • US7565575B2 patent drawing

AI summary

This document describes solutions to reduce the time of reduced data redundancy following transient disk failures that do not corrupt the disk. Beneficially, these solutions provide a way to estimate the most efficient repair strategy for the disk group, which helps to minimize the amount of time data in a disk group remains unprotected. Merely by way of example, a threshold value might specify a duration in which a disk failure should be considered transient, such that if the disk is repaired within that duration, only the stale extents on the disk need be recreated. If the disk cannot be repaired within that duration, the entire contents of the disk might be recreated on one or more other disks in the group.