USAGE OF CACHE AND WRITE TRANSACTION INFORMATION IN A STORAGE DEVICE

• US 20140143476A1
• Filed: 02/25/2013
• Published: 05/22/2014
• Est. Priority Date: 11/16/2012
• Status: Abandoned Application

• Current Assignee: SanDisk Technologies LLC (Western Digital Corporation)
• Original Assignee: SanDisk Technologies LLC (Western Digital Corporation)
• Inventors: Sela, Rotem, Shmuel, Avraham
• Application Number:
  US13/775,896
• Publication Number:
  US 20140143476A1
• Time in Patent Office: Days
• US Class Current: 711/103
• CPC Class Codes: G06F 12/0246 in block erasable memory, e.g. flash memory
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/0656 Data buffering arrangements
• CPC Class Codes: G06F 3/0679 Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]

Abstract

A method and system are disclosed for tracking write transactions in a manner to prevent corruption of file system during interruptions such as power failures between write commands. The method includes the storage device tracking transaction identifiers for write commands and delaying the update of a main memory logical-to-physical map until all of the write commands for a particular transaction have been received based on the transaction ID information. The system includes a storage device having a flash memory with a main logical-to-physical mapping data structure and a controller configured to track individual write commands of a write transaction and store data from those commands without updating the main logical-to-physical mapping data structure until all of the data for the write transaction has been received.

Claims

1. A method for managing a storage device, the method comprising:

in the storage device operatively coupled with a host, wherein the storage device includes a controller and non-volatile memory, the controller;

receiving a write command from the host;

identifying a transaction ID in the write command associated with data in the write command;

writing data from the write command to a physical location in the non-volatile memory associated with the transaction ID for the write command; and

accepting the write command only upon determining that all write commands associated with the transaction ID have been received.

2. The method of claim 1, wherein the physical location comprises a temporary physical location and accepting the write command comprises moving the data from the write command from the temporary physical location to a final physical location in the non-volatile memory.

3. The method of claim 1, wherein the storage device further comprises a main logical-to-physical mapping data structure, writing the data from the write command further comprises writing the data to the physical location without updating the main logical-to-physical mapping data structure, and accepting the write command comprises updating the main logical-to-physical mapping data structure.

4. The method of claim 1, wherein a first write command associated with the transaction ID includes data indicating a total number of write commands associated with the transaction ID and wherein determining that all the write commands have been received comprises determining if a number of received write commands associated with the transaction ID equals the total number of write commands identified in the first write command.

5. The method of claim 1, wherein a first write command associated with the transaction ID includes data indicating a total amount of data associated with the transaction ID that is to be sent to the storage device and wherein determining that all the write commands have been received comprises determining if an amount of data in received write commands associated with the transaction ID equals the total amount of data identified in the first write command.

6. The method of claim 1, wherein determining that all write commands associated with the transaction ID have been received comprises identifying a transaction ID completion event associated with a command from the host.

7. The method of claim 6, wherein the command is a write command and identifying the transaction ID completion event, comprises receiving a transaction ID completion flag as part of the write command.

8. The method of claim 6, wherein the transaction ID completion event comprises receiving a new transaction ID.

9. The method of claim 1, wherein the non-volatile memory comprises a flash memory having a cache portion and a main storage portion, and wherein writing data received in the write command to the physical location comprises writing data to the cache portion of the non-volatile memory and creating an entry in a subordinate logical-to-physical mapping data structure, separate from a main logical-to-physical mapping data structure, identifying the physical location and transaction ID.

10. The method of claim 1, wherein the storage device further comprises a volatile memory, and wherein writing data from the write command to the physical location comprises writing data to the volatile memory.

11. The method of claim 1, further comprising rejecting any data received in write commands associated with the transaction ID if the transaction associated with the transaction ID is canceled prior to completion of the transaction.

12. The method of claim 1, further comprising rejecting any data received in write commands associated with the transaction ID if a transaction termination condition is detected prior to completion of the transaction.

13. A storage device comprising:

a non-volatile memory;

and

a controller in communication with the non-volatile memory, wherein the controller is configured to;

receive a write command from a host;

identify a transaction ID in the write command associated with data in the write command;

write data from the write command to a physical location in the storage device associated with the transaction ID for the write command; and

accept the write command only upon determining that all write commands associated with transaction ID have been received.

14. The storage device of claim 13, wherein the physical location comprises a temporary physical location and the controller is configured to accept the write command by moving the data from the write command from the temporary physical location to a final physical location in the non-volatile memory.

15. The storage device of claim 13, further comprising a main logical-to-physical mapping data structure, wherein the controller is configured to write the data from the write command to the physical location without updating the main logical-to-physical mapping data structure, and wherein the controller is further configured to accept the write command by updating the main logical-to-physical mapping data structure.

16. The storage device of claim 13, wherein a first write command associated with the transaction ID includes data indicating a total number of write commands associated with the transaction ID and wherein the controller is configured to determine that all write commands have been received if a number of received write commands associated with the transaction ID equals the total number of write commands identified in the first write command.

17. The storage device of claim 13, wherein a first write command associated with the transaction ID includes data indicating a total amount of data associated with the transaction ID that is to be sent to the storage device and wherein the controller is configured to determine that all write commands have been received if an amount of data in received write commands associated with the transaction ID equals the total amount of data identified in the first write command.

18. The storage device of claim 13, wherein the controller is configured to determine that all write commands have been received relating to the transaction ID upon identification of a transaction ID completion event associated with a command received from the host.

19. The storage device of claim 13, wherein the non-volatile memory comprises a cache portion and a main storage portion, and wherein the controller is configured to write data received in the write command to the physical location by writing data to the cache portion of the non-volatile memory and creating an entry in a subordinate logical-to-physical mapping data structure, separate from the main logical-to-physical mapping data structure, identifying the physical location and transaction ID.

20. The storage device of claim 13, wherein the storage device further comprises a volatile memory, and wherein the controller is configured to write data from the write command to the physical location by writing data to the volatile memory and creating an entry in a subordinate logical-to-physical mapping data structure, separate from the main logical-to-physical mapping data structure, identifying the physical location and transaction ID.

21. A method for managing a storage device, the method comprising:

in the storage device operatively coupled with a host, wherein the storage device includes a controller, non-volatile memory and a main logical-to-physical mapping data structure, the controller;

receiving a plurality of write commands from the host;

identifying transaction identifiers (IDs) in the plurality of write commands associated with data in the write command, wherein each write command includes a transaction ID and more than one write command includes a same transaction ID;

writing data from the plurality of write commands to physical locations in the storage device, and tracking a respective transaction identifier associated with the data received in a same write command with the respective transaction identifier, without updating the main logical-to-physical mapping data structure; and

only upon determining that all write commands associated with a same respective transaction ID have been received, updating the main logical-to-physical mapping data structure to include the physical locations of the data associated with the same respective transaction ID.

22. The method of claim 21, wherein receiving the plurality of write commands comprises receiving a first plurality of write commands associated with a first transaction ID and a second plurality of write commands associated with a second transaction ID different than the first transaction ID.

23. The method of claim 22, wherein a first write command associated with the first transaction ID includes data indicating a total number of write commands associated with the first transaction ID and wherein the controller is configured to determine that all write commands associated with the first transaction ID have been received if a number of received write commands associated with the first transaction ID equals the total number of write commands identified in the first write command.

24. The method of claim 22, wherein a first write command associated with the first transaction ID includes data indicating a total amount of data associated with the first transaction ID that is to be sent to the storage device and wherein the controller is configured to determine that all write commands associated with the first transaction ID have been received if an amount of data in received write commands associated with the first transaction ID equals the total amount of data identified in the first write command.

25. The method of claim 22, wherein the controller is configured to determine that all write commands have been received relating to the first transaction ID upon receipt of a transaction ID completion flag associated with the first transaction ID from the host.