Anti-Fragile Storage with Feedback-Driven Erasure Coding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional storage systems are configured based on initial assumptions about component failure rates from manufacturers, which may not accurately reflect real-world conditions, leading to inefficiencies or increased risk of data loss due to overprotection or underprotection.

Innovation Solution

A storage system that continuously monitors actual component failure rates and dynamically adjusts its erasure coding configuration to maintain optimal reliability, using machine learning to adapt to changing conditions and ensure desired reliability metrics are met.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional storage systems use manufacturer-specified failure rates for configuration, then initial reliability assumptions are met, but actual reliability deviates due to real-world conditions causing overprotection or underprotection

Engineering Contradiction:
Improvedata reliabilityVSAvoidfailure rate accuracy
Core Design Contradiction:
ReliabilityVSMeasurement precision

Solution Approach 1:

The system continuously monitors actual component failure rates and uses this feedback to dynamically adjust erasure coding configurations. This closed-loop approach ensures that the reliability configuration accurately reflects real-world conditions rather than relying on static manufacturer specifications, resolving the discrepancy between assumed and actual failure rates

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The storage system transitions from static configuration based on manufacturer specifications to dynamic configuration that adapts to changing real-world failure rates. The system continuously adjusts erasure coding parameters based on monitored failure data, ensuring optimal reliability without overprotection or underprotection

Inventive Principle:
Principle #15Dynamics

2Reliability

If storage systems increase redundancy to ensure reliability, then data protection improves, but storage efficiency decreases due to overprotection

Engineering Contradiction:
Improvedata protectionVSAvoidstorage efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system dynamically changes erasure coding parameters (number of data chunks and parity chunks) based on actual monitored failure rates. When failure rates are lower than expected, the system reduces redundancy to improve storage efficiency. When failure rates increase, it increases redundancy to maintain data protection, thus avoiding both overprotection and underprotection

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

Instead of applying full redundancy (excessive action) based on worst-case manufacturer specifications, the system applies partial redundancy appropriate to actual observed failure rates. This ensures adequate protection while minimizing unnecessary storage overhead

Inventive Principle:
Principle #16Partial or excessive action

3Productivity

If storage systems reduce redundancy to improve efficiency, then storage capacity increases, but data loss risk increases due to underprotection

Engineering Contradiction:
Improvestorage capacityVSAvoiddata loss risk
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system uses feedback from continuous failure rate monitoring to determine appropriate redundancy levels. When failure rates remain consistently low, the system can safely reduce redundancy to improve storage capacity. When failure rates approach or exceed thresholds, the system increases redundancy to prevent data loss, thus avoiding underprotection while maximizing efficiency

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12386707B1Anti-fragile storage systems
Publication Date: 2025.08.12 VDURA INC
  • US12386707B1 patent drawing
  • US12386707B1 patent drawing
  • US12386707B1 patent drawing

AI summary

A storage system receives an initial failure rate of a storage device based on manufacturer specifications and determining a first erasure coding configuration to meet minimum reliability metrics. Data is encoded in the storage device using the first configuration. Operational data is then collected to monitor failures, and a second failure rate is determined if deviations from the initial rate exceed a predetermined threshold. Based on the updated failure rate and reliability metrics, a second erasure coding configuration, different from the first erasure coding configuration, is determined. The system then re-encodes data using the second configuration.