|
View Edit Delete |
US8533406B2 |
Claim 14.The method of claim 11, wherein receiving comprises receiving the indication from one of a file system, operating system, storage client, and storage application, and wherein the indication comprises one of a hint, a message, a command, and a directive. |
310 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
removing a mapping between the logical identifier and the physical address of the data of the specified logical identifier on the non-volatile storage device in response to the indication comprising the logical identifier, wherein removal of the mapping indicates that the data corresponding to the logical identifier does not need to be preserved on the non-volatile storage device. |
307 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
Claim 12.The method of claim 11, further comprising erasing a storage division comprising the data in a storage recovery process. |
308 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
receiving, at a storage driver configured to maintain mappings between logical identifiers and physical addresses of a non-volatile storage device, an indication comprising a logical identifier corresponding to data that does not need to be preserved on the non-volatile storage device, wherein the logical identifier is associated with a storage client data identifier, and wherein the logical identifier is mapped to a physical storage location of the data on the non-volatile storage device in an index; and |
306 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
Claim 9.The method of claim 1, wherein receiving comprises receiving the message via a block storage protocol. |
303 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
Claim 8.The method of claim 1, wherein receiving comprises receiving the message through a block storage application programming interface. |
302 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
Claim 7.The method of claim 1, wherein receiving comprises receiving the message from a block storage client. |
301 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
Claim 6.The method of claim 1, wherein indicating comprises marking the contents of the physical storage location invalid. |
300 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
Claim 5.The method of claim 1, further comprising maintaining an index of mappings between logical identifiers and physical storage locations, wherein indicating comprises removing a mapping between the logical identifier and the physical storage location from the index. |
299 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
Claim 10.The method of claim 1, further comprising erasing the contents of the physical storage location in a storage recovery process. |
304 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
Claim 13.The method of claim 11, further comprising invalidating a data packet in response to receiving the indication. |
309 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
Claim 15.An apparatus, comprising: |
311 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
a request receiver module of a storage layer for the non-volatile storage medium configured to receive an indication that a data structure, corresponding to data stored on the non-volatile storage medium, has been deleted, wherein the indication comprises a logical identifier that is associated with the data structure by a storage client, and wherein the logical identifier is mapped to a physical address of the data on the non-volatile storage medium; and |
313 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
a marking module configured to record that the data stored at the physical address mapped to the logical identifier can be erased from the non-volatile storage medium in response to receiving the indication. |
314 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
Claim 16.The apparatus of claim 15, wherein the marking module is configured to record that data stored at a physical address on the non-volatile storage medium can be erased from the non-volatile storage medium by invalidating an association between the logical identifier and the physical address. |
315 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
Claim 17.The apparatus of claim 15, wherein the marking module is configured to record that data stored at a physical address on the non-volatile storage medium can be erased from the non-volatile storage medium by deleting a mapping between the logical identifier and the physical address. |
316 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
Claim 18.The apparatus of claim 15, further comprising an index comprising mappings between logical identifiers and physical addresses on the non-volatile storage medium, wherein the marking module is configured to remove a mapping between the logical identifier and the physical addresses of the data from the index. |
317 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
Claim 19.The apparatus of claim 18, wherein the marking module is configured to delete a reference to the physical address from an index entry of the logical identifier. |
318 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
Claim 20.The apparatus of claim 18, wherein removal of the mapping indicates that data stored at the physical address can be erased from the non-volatile storage medium. |
319 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |
|
View Edit Delete |
US8533406B2 |
Claim 21.The apparatus of claim 15, wherein the marking module is configured to mark a data packet at the physical address invalid. |
320 |
Added by DJM 3 2021 |
3/24/21, 12:00 AM |