Namespace-Based Error Recovery in Data Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Error recovery operations in data storage devices often compromise data access speed, as they require repeated retries to ensure error-free data retrieval, which is undesirable for applications that can tolerate errors without significant performance impact.

Innovation Solution

Customizable error recovery settings are implemented through namespaces, allowing different data applications to be stored in namespaces with tailored error recovery configurations, balancing performance and accuracy by limiting retry operations based on specific error recovery thresholds and RAID settings.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If error recovery operations are performed with repeated retries to ensure error-free data retrieval, then data reliability is improved, but data access speed deteriorates

Engineering Contradiction:
Improvedata reliabilityVSAvoiddata access speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The patent applies local quality by implementing different error recovery settings for different namespaces. Each namespace can have customized error recovery thresholds and RAID settings tailored to the specific data type stored therein. This allows critical data to receive exhaustive error recovery while non-critical data uses limited retry operations, thereby resolving the contradiction between reliability and access speed at the local level rather than applying a uniform approach system-wide.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent segments the storage system into multiple namespaces, each with independent error recovery configurations. This segmentation allows the system to apply different error recovery strategies to different data portions, enabling critical data to have high reliability through repeated retries while non-critical data accepts faster access with tolerable error levels, thus resolving the overall contradiction between reliability and speed.

Inventive Principle:
Principle #1Segmentation

2Measurement precision

If exhaustive error recovery is applied to all data, then data accuracy is improved, but system efficiency deteriorates

Engineering Contradiction:
Improvedata accuracyVSAvoidsystem efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent implements local quality by allowing each namespace to have customized error recovery settings based on the specific accuracy requirements of the stored data. Critical data in certain namespaces receives exhaustive error recovery with high retry thresholds, while non-critical data in other namespaces uses limited error recovery, thereby maintaining high accuracy where needed while preserving overall system efficiency.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent applies dynamics by making error recovery settings adjustable and configurable per namespace rather than fixed system-wide. This allows the system to dynamically adapt error recovery intensity to match the specific requirements of different data types, optimizing the balance between data accuracy and system efficiency based on actual operational needs.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20230359535A1Custom error recovery in selected regions of a data storage device
Publication Date: 2023.11.09 MICRON TECHNOLOGY INC
  • US20230359535A1 patent drawing
  • US20230359535A1 patent drawing
  • US20230359535A1 patent drawing

AI summary

A memory sub-system having non-volatile media on which multiple namespaces are allocated. A command from a host system has an identification of a namespace and at least one error recovery parameter. A controller of the memory sub-system configures the namespace on the non-volatile media according to the at least one error recovery parameter, stores the at least one error recovery parameter in association with the namespace, and controls error recovery operations for data access in the namespace in accordance with the at least one error recovery parameter stored in association with the namespace.