Dave's PCF WIP: Paragraphs

Paragraphs

Actions	Application	Content	Paragraph Number	Notes	Modified
		Content		Paragraph Number	Notes	Any Field
View Edit Delete	US8533406B2	Disclosed herein are embodiments of apparatuses and/or systems for managing a non-volatile storage medium, comprising a request receiver module configured to receive an indication identifying data that can be erased from a non-volatile storage medium, wherein the indication identifies the data using a logical identifier associated with the data, and a marking module 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 in response to receiving the indication.	16	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	In some embodiments, the methods disclosed herein may further comprise receiving the message from a block storage client, such as a file system, operating system, application, client, or the like. The message may be received through a block storage application programming interface, block storage protocol, or the like.	15	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	In some embodiments, the methods disclosed herein may further comprise erasing the contents of the physical storage location in a storage recovery process, such as garbage collection or the like. The storage recovery process may comprise erasing a storage division comprising the physical storage location (e.g., erase block, logical erase block, or the like).	14	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	Methods for managing a non-volatile storage medium may further comprise receiving a hint or other indication that data of a specified logical identifier does not need to be preserved on a non-volatile storage device, and removing a mapping between the specified logical identifier and a physical address of the data of the specified logical identifier on the non-volatile storage device in response to the hint, wherein removal of the mapping indicates that the data does not need to be preserved on the non-volatile storage device. The methods may further comprise invalidating a data packet in response to the hint.	13	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	The methods may further comprise maintaining an index of mappings between logical identifiers and physical storage locations, and that the contents of the physical storage location do not need to be preserved may comprise removing a mapping between the logical identifier and the physical storage location from the index.	12	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	Indicating that the contents of the physical storage location do not need to be preserved may comprise deleting an index entry that associates the logical identifier with the physical storage location, deleting a mapping between the logical identifier and the physical storage location, invalidating an association between the logical identifier and an address of the physical storage location, and/or marking the contents of the physical storage location invalid.	11	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	An empty-block directive may be added to the block storage APIs and/or protocols. File systems and other clients of the API and/or protocol may be enhanced to issue these directives. For example, when a file is deleted, the file-system can issue an “empty-block” directive for the blocks that contained the data for that file, indicating that the contents of the blocks do not need to be retained (e.g., the blocks can be considered free space). This directive may serve a secondary security purpose by incorporating a flag to indicate that the existing data should be destroyed.	243	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	Claim 3.The method of claim 1, wherein indicating comprises deleting a mapping between the logical identifier and the physical storage location.	297	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	Claim 2.The method of claim 1, wherein indicating comprises deleting an index entry that associates the logical identifier with the physical storage location.	296	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	indicating that contents of the physical storage location do not need to be preserved on the non-volatile storage medium in response to the message.	295	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	receiving a message, at a storage controller, comprising a logical identifier, the message indicating that a storage client has deleted a block associated with the logical identifier such that data of the logical identifier does not need to be preserved on a non-volatile storage medium, wherein the logical identifier is associated with a physical storage location on the non-volatile storage medium; and	294	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	Claim 1.A method for managing data stored on non-volatile storage media, the method comprising:	293	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	In one embodiment, the token directive generation module 1002 generates both a token directive and a secure erase command in response to a request to overwrite existing data on the storage device 150. The existing data includes data identified on the storage device 150 with the same data segment identifier as the data segment identifier in the token directive. Typically, a request to overwrite data is sent where it is not sufficient to merely mark data as invalid or garbage, delete a pointer to the data, or other typical delete operation, but where the data is required to be overwritten in such a way that that the data is not recoverable. For example, the request to overwrite the data may be required where data is considered sensitive information and must be destroyed for security reasons.	255	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	Typically, when data is no longer useful it may be erased. In many file systems, an erase command deletes a directory entry in the file system while leaving the data in place in the storage device containing the data. Typically, a data storage device is not involved in this type of erase operation. Another method of erasing data is to write zeros, ones, or some other null data character to the data storage device to actually replace the erased file. However, this is inefficient because valuable bandwidth is used to transmit the data for the overwrite operation. In addition, space in the storage device is taken up by the data used to overwrite invalid data.	247	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	In some embodiments, the storage driver may be configured to recognize zero blocks as they are being written and instead “clear” their contents, effectively compressing the zero blocks. The zero blocks may not be transferred to the storage device, further reducing workload. Identifying blocks that are not all zeros is a relatively low overhead operation.	246	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	File systems may write zeros to unused blocks to indicate that the blocks do not hold data that needs to be preserved and/or for security reasons. Empty-block directives or hints sent by the file system may be used in place of these operations. In some embodiments, a data segment token may be stored in place of the sequence of zeros (or other data pattern) to signify that the blocks are not in use. This may be especially useful in block storage applications. Blocks are always considered valid, their contents needing to be preserved, even if the client (e.g., file system) is not currently using the blocks to store valid data. Many file systems are diligent about zeroing out blocks that are not actually storing valid data. The blocks may be zeroed out for security reasons (e.g., prevent read before write hazards). The compression module described above may be used to reduce the storage requirements of these types of sequences. Alternatively, or in addition, an API may be provided to identify unused blocks (e.g., an API to “throw away the contents of these blocks” or a “clear” command). Subsequent requests to read data of such blocks may return zeros.	245	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	Alternatively, or in addition, agents may be configured to write all zeros to the blocks whose contents are no longer needed. The underlying block storage system can recognize all-zero blocks and avoid having to actually store the all-zero content. Subsequent reads can return the same all-zero data. The garbage-collection-based storage systems may treat the zeroed blocks as free space.	244	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	Embodiments of methods for managing a non-volatile storage media are disclosed. The methods may comprise receiving a message comprising a logical identifier corresponding to data that does not need to be preserved on a non-volatile storage medium, and indicating that that contents of a physical storage location on the non-volatile storage medium corresponding to the logical identifier do not need to be preserved on the non-volatile storage medium in response to the message.	10	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	Most agents that use block storage do not need the contents of every block to be preserved. File systems, for example, are rarely filled to near the capacity of the underlying block storage device(s). If the file system were to supply a hint to the block storage regarding which specific blocks do not hold data that needs to be preserved, the efficiency of the garbage collection on the underlying block storage system could be improved. However, customizing file-systems and other agents to integrate directly with a garbage-collection-based storage system does not get the benefit of using decoupled, commercially hardened, and robust block APIs and protocols.	242	Added by DJM 3 2021	3/24/21, 12:00 AM
View Edit Delete	US8533406B2	The performance of garbage-collection-based systems may be impacted by the availability of free storage space. Block-based storage protocols, such as SCSI and/or SATA, however, presume that every block is allocated, and that the contents of the blocks need to be preserved. As such, these blocks may not be considered to be free space. As a result, reserve space may be set aside to create free space. However, setting aside the reserve space may reduce the available capacity of the storage device, and the reserved space may not be large enough to allow the garbage-collection system to operate efficiently.	241	Added by DJM 3 2021	3/24/21, 12:00 AM

Page 4 of 5, showing 20 record(s) out of 87 total