Pre-emptive operations for faster XOR recovery and relocation
During data storage device operation, data of multiple blocks of a non-volatile memory device, logically grouped as a jumboblock, may be protected by an exclusive or (XOR) signature, where the XOR signature may be used to recover data of a block of the multiple blocks. During a recovery/relocation operation, data of the jumboblock is read from the non-volatile memory device during the recovery of the lost data and again when the data is relocated. However, because the data read during data storage device operation is temporarily stored in a volatile memory device, the controller utilizes the relevant data stored in the volatile memory device and the data stored in the non-volatile memory device to recover corrupted data. Thus, the amount of reads from the non-volatile memory device decreases due to the relevant data is read from the volatile memory device, which may improve data storage device performance.
1. A data storage device, comprising:
a non-volatile memory device; and
a controller coupled to the non-volatile memory device and a volatile memory device, wherein the controller is configured to:
read data from a block of a first plurality of blocks of the non-volatile memory device responsive to executing a read command received from a host device;
determine that a health of one or more blocks of the plurality of blocks of the non-volatile memory device has reached a recovery/relocation threshold, wherein the one or blocks are in a same exclusive or (XOR) signature as the block;
store the block in the volatile memory device responsive to providing data read from the block to the host device, wherein a health of the block is determined to have reached the recovery/relocation threshold; and
perform a recovery/relocation operation, wherein the recovery/relocation operation comprises:
recovering the stored block from the volatile memory device,
recovering the one or more blocks remaining in the non-volatile memory device, wherein the one or more blocks remaining comprise the one or more blocks except for the stored block; and
relocating the recovered stored block and the one or more blocks remaining to a second plurality of blocks of the non-volatile memory device, wherein the second and the first plurality of blocks are separate and distinct.
2. The data storage device of claim 1 , wherein determining that the health of the one or more blocks comprises determining, for each of the one or more blocks, one or more of:
a program erase count (PEC) of each block of the one or more blocks;
a bit error rate (BER) of each block of the one or more blocks;
a read disturb metric of each block of the one or more blocks;
a temperature of each block of the one or more blocks;
a cross-temperature of each block of the one or more blocks; and
an amount of power consumption of each block of the one or more blocks.
3. The data storage device of claim 1 , wherein the volatile memory device is either:
a host memory buffer (HMB) of the host device;
a static random access memory (SRAM) of the controller; or
a dynamic random access memory (DRAM) of the controller.
4. The data storage device of claim 1 , wherein the recovery/relocation threshold is a predetermined value less than an actual recovery/relocation threshold, wherein the controller is configured to initiate the recovery/relocation operation upon reaching the actual recovery/relocation threshold.
5. The data storage device of claim 4 , wherein the controller is further configured to:
determine that a block of the one or more blocks has reached the actual recovery/relocation threshold;
determine that at least one block of the one or more blocks is stored in the volatile memory device;
recover/relocate the at least one block of the one or more blocks from the volatile memory device; and
recover/relocate each other block other than the at least one block of the one or more blocks from the non-volatile memory device.
6. The data storage device of claim 5 , wherein less than all of the blocks of the one or blocks are read from the non-volatile memory device during the recovery/relocation operation.
7. The data storage device of claim 1 , wherein the XOR signature is utilized to recover data of the block of the one or more blocks during the recovery/relocation operation.
8. A data storage device, comprising:
a non-volatile memory device; and
a controller coupled to the non-volatile memory device and a volatile memory device, wherein the controller is configured to:
determine that at least a partial block failure has occurred to a block of a plurality of blocks of the non-volatile memory device, wherein:
the block is part of a set of blocks that are associated with an exclusive or (XOR) signature; and
the XOR signature is used to recover one or more pages of the block of the set of blocks associated with the XOR signature; and
perform a recovery/relocation operation to recover at least one page of the block that has failed using the XOR signature, wherein the recovery/relocation operation comprises
determining that the at least one page of the block that has failed using the XOR signature exists in the volatile memory device;
recovering the at least one page of the block that has failed using the XOR signature from the volatile memory device;
recovering a remaining number of pages of the block from the non-volatile memory device; and
relocating the at least one recovered page of the block from the volatile memory device, and the remaining number of pages of the block from the non-volatile memory device to another block of the non-volatile memory device.
9. The data storage device of claim 8 , wherein recovering the at least one page of the block that has failed using the XOR signature comprises reading the at least one page of the block that has failed using the XOR signature from the volatile memory device once.
10. The data storage device of claim 9 , wherein recovering the remaining number of pages of the block of the set of blocks from the non-volatile memory device comprises reading the remaining number of pages of the block of the set of blocks twice.
11. The data storage device of claim 8 , wherein the controller is further configured to:
determine which pages of the block of the set of blocks are stored in the volatile memory device responsive to determining that the partial block failure has occurred to the block of the plurality of blocks of the non-volatile memory device.
12. The data storage device of claim 8 , wherein the controller is further configured to:
receive a read command for another block of the set of blocks stored in the non-volatile memory device; and
determine a health metric of one or more blocks of the set of blocks.
13. The data storage device of claim 12 , wherein the controller is further configured to:
determine that the health metric of at least a block of the one or more blocks has reached or exceeded a predetermined threshold value; and
store the data of the another block associated with the read command in the volatile memory device.
14. The data storage device of claim 13 , wherein the controller is further configured to:
erase the at least one page of the block that has failed using the XOR signature from the volatile memory device responsive to the performance of the recovery/relocation operation.
15. The data storage device of claim 8 , wherein the volatile memory device is a host memory buffer (HMB) of a host device.
16. The data storage device of claim 8 , wherein the volatile memory device is either a static random access memory (SRAM) of the controller or a dynamic random access memory (DRAM) coupled to the controller.
17. The data storage device of claim 8 , wherein the at least the partial block failure is a full block failure.
18. A data storage device, comprising:
means for storing non-volatile data; and
a controller coupled to the means for storing non-volatile data and means for storing volatile data, wherein the controller is configured to:
store data read from the means for storing non-volatile data in the means for storing volatile data; and
utilize the data stored in the means for storing volatile data and data stored in the means for storing non-volatile data to recover data having a read failure, wherein the utilizing comprises:
determining that a portion of the data stored in the means for storing non-volatile data is unrecoverable;
determining that the portion of the data exists in the means for storing volatile data;
recovering the portion of the data from the means for storing volatile data;
recovering a remaining portion of the data from the means for storing non-volatile data; and
relocating the recovered portion of the data, from the means for storing volatile data, and the remaining portion of the data, from the means for storing non-volatile data, to another location of the means for storing non-volatile data.
19. The data storage device of claim 18 , wherein the data stored in the means for storing volatile data and the data stored in the means for storing non-volatile data utilized to recover data having the read failure are associated with a same exclusive or (XOR) signature.
20. The data storage device of claim 19 , wherein storing the data read from the means for storing non-volatile data in the means for storing volatile data is responsive to determining that the data stored in the means for storing non-volatile data associated with a same XOR signature has reached or exceeded a health metric threshold.