Burst Pool Repurposing to Delay Storage Device Read-Only Mode
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing storage devices enter a read-only mode prematurely due to faulty blocks, leading to reduced write capacity and end-of-life status, with current solutions like reducing write capacity or over-provisioning spare blocks being costly or adversely impacting performance.
Innovation Solution
The storage device is divided into a main area pool for host data, a burst pool for peak write operations, and a control pool for control information, with a controller executing protocols to manage faulty blocks and repurpose blocks to prevent entry into read-only mode.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If faulty blocks are removed from the memory device, then the reliability of write operations is improved, but the write capacity of the storage device is reduced
Solution Approach 1:
The memory device blocks are segmented into three distinct pools: main area pool for standard host data, burst pool for peak write operations and spare blocks, and control pool for control information. This segmentation allows faulty blocks to be isolated and managed separately while maintaining overall system reliability and capacity.
Solution Approach 2:
The system dynamically changes the status parameter of blocks between different pools based on their health state. When blocks in the main area pool become faulty, they are removed and their capacity is reallocated to the burst pool, changing the parameter distribution to maintain write capacity while ensuring reliability.
2Duration of action of moving object
If over-provisioning of spare blocks is implemented, then the lifespan of the storage device is extended, but the cost increases
Solution Approach 1:
The burst pool serves multiple functions: it acts as a buffer for peak write operations, provides spare blocks for replacing faulty blocks, and can be dynamically expanded by reallocating faulty blocks from the main area pool. This multi-functionality extends device lifespan without requiring additional over-provisioned spare blocks, avoiding increased costs.
3Quantity of substance
If blocks are repurposed from burst pool to main area pool, then the write capacity is maintained, but the performance during peak write operations may be impacted
Solution Approach 1:
The system dynamically adjusts the allocation of blocks between pools based on real-time conditions. When the storage device approaches end-of-life status, faulty blocks are reallocated from the main area pool to the burst pool, dynamically maintaining write capacity while preserving peak write performance through the burst pool's dedicated spare blocks.
Data Source
AI summary
A storage device postpones entry into a read-only mode due to faulty blocks that cannot be written to on a memory device. The memory device is divided into blocks. Blocks used for storing host data are placed in a main area pool, blocks used for storing host data and for peak write operations are placed in a burst pool, and blocks used for storing control information are placed in the control pool. A controller executes a read-only mode extension protocol to determine when a number of faulty blocks in the main area pool, control pool, or burst pool is approaching a threshold for placing the storage device in a read-only mode. If the storage device is approaching the read-only mode, the controller reduces and/or repurposes a number of the blocks used for storing host data in the burst pool to prevent the storage device from entering the read-only mode phase.