Dave's PCF WIP: Paragraphs

Edit Paragraph

Application

Application Number

Matter Number

Paragraph Number

Content

In another embodiment, the secure erase module 1320 overwrites the existing data during a storage space recovery operation. For example, if the storage device 150 is a solid-state storage device 102, as described above, the storage space recovery operation may be related to the garbage collection describe in relation to the apparatus 800 depicted in FIG. 8. However, a storage space recovery operation involving a request to overwrite the existing data would typically be expedited so that the storage location where the existing data is stored is necessarily recovered prior to any confirmation message is sent by the erase confirmation module 1322. In one embodiment, the existing data is marked or otherwise identified to indicate that a secure erase has been requested. The confirmation message would typically not be sent until the existing data marked for erasure has been overwritten and made non-recoverable. In another embodiment, the secure erase module 1320 merely marks the existing data as invalid for later storage space recovery. In another embodiment, the secure erase updates an index to indicate that the existing data is invalid and prevents access to this data until the data is overwritten during later storage space recovery.

Reference Case 1

Reference Case 2

Notes

Raw Data

<w:p><w:pPr><w:pStyle w:val="TPSBody100"/></w:pPr><w:r><w:t xml:space="preserve">In another embodiment, the secure erase module </w:t></w:r><w:r><w:t>1320</w:t></w:r><w:r><w:t xml:space="preserve"> overwrites the existing data during a storage space recovery operation. For example, if the storage device </w:t></w:r><w:r><w:t>150</w:t></w:r><w:r><w:t xml:space="preserve"> is a solid-state storage device </w:t></w:r><w:r><w:t>102</w:t></w:r><w:r><w:t xml:space="preserve">, as described above, the storage space recovery operation may be related to the garbage collection describe in relation to the apparatus </w:t></w:r><w:r><w:t>800</w:t></w:r><w:r><w:t xml:space="preserve"> depicted in </w:t></w:r><w:r><w:t>FIG. 8</w:t></w:r><w:r><w:t xml:space="preserve">. However, a storage space recovery operation involving a request to overwrite the existing data would typically be expedited so that the storage location where the existing data is stored is necessarily recovered prior to any confirmation message is sent by the erase confirmation module </w:t></w:r><w:r><w:t>1322</w:t></w:r><w:r><w:t xml:space="preserve">. In one embodiment, the existing data is marked or otherwise identified to indicate that a secure erase has been requested. The confirmation message would typically not be sent until the existing data marked for erasure has been overwritten and made non-recoverable. In another embodiment, the secure erase module </w:t></w:r><w:r><w:t>1320</w:t></w:r><w:r><w:t xml:space="preserve"> merely marks the existing data as invalid for later storage space recovery. In another embodiment, the secure erase updates an index to indicate that the existing data is invalid and prevents access to this data until the data is overwritten during later storage space recovery.</w:t></w:r></w:p>