Electronic system with storage management mechanism and method of operation thereof

• US 9,098,399 B2
• Filed: 08/21/2012
• Issued: 08/04/2015
• Est. Priority Date: 08/31/2011
• Status: Active Grant

• Current Assignee: SanDisk Technologies LLC (Western Digital Corporation)
• Original Assignee: Smart Storage Systems Incorporated (Western Digital Corporation)
• Inventors: Ellis, Robert W., Fitzpatrick, James, Higgins, James
• Primary Examiner(s): Bradley, Matthew
• Assistant Examiner(s): Goldschmidt, Craig
• Application Number:
  US13/590,826
• Publication Number:
  US 20130054881A1
• Time in Patent Office: 1,078 Days
• Field of Search: 711/165
• US Class Current: 1/1
• CPC Class Codes: G06F 12/0246 in block erasable memory, e.g. flash memory
• CPC Class Codes: G06F 2212/7205 Cleaning, compaction, garbage collection, erase control
• CPC Class Codes: G06F 3/0605 by facilitating the interaction with a user or administrator
• CPC Class Codes: G06F 3/0647 Migration mechanisms
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Abstract

A method of operation of an electronic system includes: forming a superblock by organizing an erase block according to a wear attribute; detecting a trigger count of the wear attribute of the superblock; updating a metadata table with the trigger count; and triggering a recycling event of the superblock based on the metadata table.

Claims

1. A method of operation of an electronic system comprising:

forming a plurality of superblocks from a set of erase blocks by organizing the set of erase blocks according to a wear attribute of each of the erase blocks in the set of erase blocks, each superblock comprising a plurality of erase blocks from the set of erase blocks;

for a respective superblock of the plurality of superblocks;

detecting a trigger count of the wear attributes of the erase blocks of the respective superblock;

updating a metadata table with the trigger count; and

in accordance with the trigger count meeting or exceeding a recycle threshold, triggering a recycling event of the respective superblock.

2. The method as claimed in claim 1 wherein detecting the trigger count of the wear attributes of the erase blocks of the respective superblock includes identifying a read count, a write age, a leakage, or a combination thereof from an erase block of the respective superblock.

3. The method as claimed in claim 1 further comprising generating a condition table for storing the trigger count from the metadata table during a power down.

4. The method as claimed in claim 1, wherein the trigger count is a highest value of the wear attributes of the plurality of erase blocks comprising the respective superblock.

5. The method as claimed in claim 1 further comprising:

detecting the recycling event; and

resetting the trigger count for the respective superblock based on the recycling event.

6. The method as claimed in claim 1, wherein each erase block of the respective superblock has a wear attribute value, and the trigger count is a highest value of the wear attribute for the plurality of erase blocks comprising the respective superblock.

7. The method as claimed in claim 1, including:

detecting a bit error count of the respective superblock;

wherein triggering the recycling event includes triggering the recycling event of the respective superblock in accordance with the bit error count meeting or exceeding the recycle threshold.

8. The method as claimed in claim 1, including:

detecting a program time of the respective superblock;

wherein triggering the recycling event includes triggering the recycling event of the respective superblock in accordance with the program time meeting or exceeding the recycle threshold.

9. The method as claimed in claim 3 further comprising:

detecting a power up; and

updating the metadata table with the condition table during the power up.

10. An electronic system comprising:

a plurality of non-volatile memory devices including a set of erase blocks; and

a memory controller including one or more processors and memory storing software for execution by the one or more processors, the software including;

a block module for forming a plurality of superblocks from a set of erase blocks by organizing the set of erase blocks according to a wear attribute of each of the erase blocks in the set of erase blocks, each superblock comprising a plurality of erase blocks from the set of erase blocks;

a table module, coupled to the block module, for detecting a trigger count of the wear attributes of the erase blocks of a respective superblock of the plurality of superblocks;

an update module, coupled to the table module, for updating a metadata table with the trigger count;

a threshold module, coupled to the table module, for detecting the trigger count meeting or exceeding a recycle threshold; and

a recycle module, coupled to the update module, for triggering a recycling event of the respective superblock in accordance with the trigger count meeting or exceeding the recycle threshold.

11. The system as claimed in claim 10 wherein the table module is for identifying a read count, a write age, a leakage, or a combination thereof from an erase block of the respective superblock.

12. The system as claimed in claim 10 further comprising a condition module, coupled to the table module, for generating a condition table for storing the trigger count from the metadata table during a power down.

13. The system as claimed in claim 10, wherein the trigger count is a highest value of the wear attributes of the plurality of erase blocks comprising the respective superblock.

14. The system as claimed in claim 10 further comprising a reset module, coupled to the recycling module, for resetting the trigger count for the respective superblock based on the recycling event.

15. The system as claimed in claim 10, wherein each erase block of the respective superblock has a wear attribute value, and the trigger count is a highest value of the wear attribute for the plurality of erase blocks comprising the respective superblock.

16. The system as claimed in claim 10,

wherein the threshold module is for detecting a bit error count of the respective superblock;

and

wherein the recycle module is for triggering the recycling event of the respective superblock in accordance with the bit error count meeting or exceeding the recycle threshold.

17. The system as claimed in claim 10,

wherein the threshold module is for detecting a program time of the respective superblock;

and

wherein the recycle module is for triggering the recycling event of the respective superblock in accordance with the program time meeting or exceeding the recycle threshold.

18. The system as claimed in claim 10 further comprising:

a status module, coupled to the table module, for detecting a power up; and

wherein;

the update module is for updating the metadata table with the condition table during the power up.