Data relocation

#This disclosure is generally related to data storage devices and more particularly to performing data relocation operations.

#Non-volatile data storage devices, such as flash solid state drive (SSD) memory devices or removable storage cards, have allowed for increased portability of data and software applications. Flash memory devices can enhance data storage density by storing multiple bits in each flash memory cell. For example, Multi-Level Cell (MLC) flash memory devices provide increased storage density by storing 2 bits per cell, 3 bits per cell, 4 bits per cell, or more. Increasing the number of bits per cell and reducing device feature dimensions may increase a storage density of a memory device.

#During execution of a relocation operation to relocate data from a first portion of a memory device to a second portion of the memory device, a data storage device may temporarily store data (that is to be relocated) to a portion of memory on an access device, such as a host memory buffer (HMB) of the access device. The data storage device may subsequently read the data stored at the HMB and write it to the second portion, thereby completing the relocation operation. However, the data stored in the HMB may become corrupted or may be overwritten, resulting in incorrect or erroneous data being written to the memory device.

#FIG. 1 is a block diagram of an illustrative example of a system including a data storage device configured to perform a relocation operation that includes storing data to a HMB and generating parity bits based on data read from the HMB.

#FIG. 2 is a flow diagram of a particular example of method of operation that may be performed by the data storage device of FIG. 1.

#FIG. 3A is a block diagram of an illustrative example of a non-volatile memory system including a controller configured to perform the relocation operation of FIG. 1.

#Particular examples in accordance with the disclosure are described below with reference to the drawings. In the description, common features are designated by common reference numbers. As used herein, “exemplary” may indicate an example, an implementation, and/or an aspect, and should not be construed as limiting or as indicating a preference or a preferred implementation. Further, it is to be appreciated that certain ordinal terms (e.g., “first” or “second”) may be provided for identificatoin and ease of reference and do not necessarily imply physical characteristics or ordering. Therefore, as used herein, an ordinal term (e.g., “first,” “second,” “third,” etc.) used to modify an element, such as a structure, a component, an operation, etc., does not necessarily indicate priority or order of the element with respect to another element, but rather distinguishes the element from another element having a same name (but for use of the ordinal term). In addition, as used herein, indefinite articles (“a” and “an”) may indicate “one or more” rather than “one.” As used herein, a structure or operation that “comprises” or “includes” an element may include one or more other elements not explicitly recited. Further, an operation performed “based on” a condition or event may also be performed based on one or more other conditions or events not explicitly recited.

#FIG. 1 depicts an illustrative example of a system 100 that includes a data storage device 102 and an access device 170 (e.g., a host device or another device). The data storage device 102 is configured to perform a relocation operation as described further herein.

#The data storage device 102 and the access device 170 may be coupled via a connection (e.g., a communication path 181), such as a bus or a wireless connection. The data storage device 102 may include a first interface 132 (e.g., an access device or host interface) that enables communication via the communication path 181 between the data storage device 102 and the access device 170.