Systems and methods for identifying storage resources that are not in use
An apparatus, system, and method are disclosed for managing a non-volatile storage medium. A storage controller receives a message that identifies data that no longer needs to be retained on the non-volatile storage medium. The data may be identified using a logical identifier. The message may comprise a hint, directive, or other indication that the data has been erased and/or deleted. In response to the message, the storage controller records an indication that the contents of a physical storage location and/or physical address associated with the logical identifier do not need to be preserved on the non-volatile storage medium.
1. A method for managing data in a NAND flash storage system, the method comprising:
sending, by a host processor, an empty-block directive including a logical identifier comprising data deleted by the host processor;
receiving, at a solid-state storage controller maintaining a block mapping table between logical identifiers and physical storage locations of the NAND flash memory, the empty block directive including the logical identifier, wherein the logical identifier is associated, in the block mapping table, with a physical storage location comprising data deleted by the host processor;
updating, by the solid state storage controller, the block mapping table to indicate that the physical storage location associated with the logical identifier comprises data deleted by the host;
sending, by the host processor, a read command requesting to read data associated with the logical identifier included in the empty block directive; and
returning, from the solid-state storage controller to the host processor, a data string comprising data of a predetermined logic level, based on the updated block mapping table, in response to the read command requesting to read data associated with the logical identifier included in the empty block directive, wherein the data of the predetermined logic level indicates that the data associated with the logical block identifier is deleted.
2. The method of claim 1 wherein the predetermined logic level is zero.
3. The method of claim 1 further comprising:
determining that the empty-block directive further includes an indication that data associated with the logical identifier should be overwritten; and
overwriting the data associated with the logical identifier.
4. The method of claim 1 wherein the empty-block directive is part of a block storage protocol.
5. The method of claim 1 wherein the empty-block directive is received through an application programming interface.
6. The method of claim 1 wherein the empty-block directive is received from a file system.
7. The method of claim 1 , wherein the empty-block directive is received from a storage client.
8. The method of claim 1 , further comprising performing garbage collection on storage locations in the flash storage system.
9. The method of claim 8 , wherein performing garbage collection comprises:
copying a block containing data to be preserved from an erase block, wherein the erase block comprises at least one block containing data to be preserved and blocks containing data that do not need to be preserved, and
erasing data from the erase block.
10. The method of claim 9 , further comprising writing new data to the erased erase block.
11. The method of claim 1 , wherein the NAND flash storage system is an append-only storage system.
12. A system, comprising:
a host processor configured to:
send an empty block directive, wherein the empty block directive includes a logical identifier for data to be deleted; and
send a read command requesting to read data associated with a logical identifier;
a NAND flash memory; and
a solid-state storage controller configured to:
maintain a block mapping table between logical identifiers and physical storage locations of the NAND flash memory;
receive an empty-block directive from the host processor, the empty block directive including a logical block identifier associated, in the block mapping table, with one or more physical storage locations of the NAND flash memory;
update the block mapping table to indicate that the one or more locations comprise data deleted by the host;
return, from the solid-state storage controller to the host processor, a data string comprising data of a predetermined logic level, based on the updated block mapping table, in response to a read command requesting to read data associated with the logical block identifier, wherein the data of the predetermined logic level indicates that the data associated with the logical block identifier is deleted.
13. The system of claim 12 , wherein the predetermined logic level is zero.
14. The system of claim 12 , wherein the storage controller is further configured to:
determine that the empty-block directive includes an indication that data associated with the block identifier should be overwritten; and
overwrite the data associated with the block identifier.
15. The system of claim 12 , wherein the empty-block directive is part of a block storage protocol.
16. The system of claim 12 , wherein the empty-block directive is received through an application programming interface.
17. The system of claim 12 , wherein the empty-block directive is received from a file system.
18. The system of claim 12 , wherein the empty-block directive is received from a storage client.
19. The system of claim 12 , wherein the storage controller is further configured to perform garbage collection on storage locations in the NAND flash memory.
20. The system of claim 12 , wherein the system is an append-only storage system.