Retry History Table for Data Storage Error Correction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Data storage devices face inefficiencies in retry operations due to the need for multiple retry procedures and the time-consuming nature of these processes, especially in high-throughput applications like audio/video data storage, where errors can occur due to various media irregularities and deterioration.
Innovation Solution
A method and device that utilize a retry history table and statistics table to determine the sequence of retry procedures, avoiding unsuccessful procedures and efficiently selecting the next retry operation based on previous performance data, allowing for quicker error correction and improved throughput.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple retry procedures are performed to correct errors, then error correction capability is improved, but operation time increases
Solution Approach 1:
The system performs preliminary actions by maintaining a retry history table that pre-records which retry procedures have already been attempted for each zone. When an error is detected, the system queries this table beforehand to avoid repeating unsuccessful procedures, thus reducing operation time while maintaining error correction capability.
Solution Approach 2:
The system implements feedback mechanisms by continuously updating the retry history table with results of performed retry procedures. This feedback loop allows the system to learn from past operations and make informed decisions about which retry procedures to attempt next, optimizing the balance between error correction and operation time.
2Reliability
If retry procedures are performed sequentially without optimization, then thorough error correction is achieved, but throughput decreases
Solution Approach 1:
The system performs preliminary查询 of the retry history table before executing retry procedures to identify which procedures have already been attempted. This preliminary action enables the system to skip unnecessary procedures and proceed directly to untried methods, maintaining thorough error correction while improving data throughput.
Solution Approach 2:
The system applies skipping by rapidly bypassing retry procedures that have already been unsuccessfully attempted, as recorded in the retry history table. This allows the system to rush through the retry process by focusing only on untried procedures, thereby maintaining error correction thoroughness while significantly improving throughput.
3Productivity
If retry history tracking is implemented, then retry efficiency is improved, but device complexity increases
Solution Approach 1:
The system segments the retry management function into distinct components: a retry history table for storing procedural information, a query mechanism for retrieving past attempts, and an update mechanism for recording new results. This segmentation improves retry efficiency while keeping each component simple and manageable.
Solution Approach 2:
The retry history table serves as an intermediary data structure that mediates between error detection and retry procedure execution. This intermediary layer simplifies the overall system by centralizing the tracking function in a single, manageable table rather than dispersing complexity throughout the error handling logic.
Data Source
AI summary
A method of performing a retry procedure may begin with detecting an error in a first zone of a data storage medium. Upon detecting the error, it is determined whether any retry procedure of a sequence of retry procedures has been performed upon detecting a previous error in the first zone. If a first retry procedure of the sequence was unsuccessfully performed upon detecting the previous error, there is performed a second retry procedure that follows next after the first retry procedure in the sequence.