Host and storage system for securely deleting files and operating method of the host

Patent metadata

Field	Value
Publication number	US-11657022-B2
Application number	US-202117376225-A
Country	US
Kind code	B2
Filing date	Jul 15, 2021
Priority date	Jul 26, 2016
Publication date	May 23, 2023
Grant date	May 23, 2023

Abstract

An operating method of a host includes receiving a request for secure deletion of a first file stored in a storage system, providing an invalidation command to the storage system for invalidating data of the first file, providing an erase command to the storage system for erasing invalidated data included in the storage system, and performing a deletion operation, which is executable on an operating system of the host, on the first file which is deleted by the erase command.

First claim

What is claimed is:

1. A storage system comprising:
a memory device configured to store data of a first file and a second file;
a history table configured to store information associated with invalid data of the first file and the second file; and
a controller configured to perform a first deletion operation and a second deletion operation on the first file based on a secure deletion on the first file and a third deletion operation on the second file based on a normal deletion on the second file,
wherein the first deletion operation includes invalidation of the data of the first file and physical erasure of the invalid data of the first file by referring to the history table, the second deletion operation is performed based on a control of an operating system (OS) of a host after the first deletion operation is completed, and
wherein the third deletion operation is performed based on the control of the OS of the host before erasure of invalid data of the second file is performed.

2. The storage system of claim 1 , wherein the memory device is further configured to store metadata of the first file.

3. The storage system of claim 1 , wherein the first deletion operation includes the invalidation of the data of the first file in response to a first command and the physical erasure of the invalid data of the first file by referring to the history table in response to a second command.

4. The storage system of claim 1 , further comprising an erase status determinator configured to determine an erase processing status of the invalid data of the first file.

5. The storage system of claim 4 , wherein the erase status determinator is further configured to generate a determination result based on determining an erase processing status of the invalid data of the first file.

6. The storage system of claim 5 , wherein the determination result indicates a ratio of the invalid data of the first file which is erase-completed to the whole invalid data to be erased.

7. The storage system of claim 6 , wherein the controller is further configured to perform the physical erasure of the invalid data of the first file based on the determination result.

8. The storage system of claim 5 , wherein the determination result indicates a time needed for the physical erasure of the invalid data of the first file.

9. The storage system of claim 8 , wherein the controller is further configured to perform the physical erasure of the invalid data of the first file based on the determination result.

10. The storage system of claim 1 , wherein the controller performs the third deletion operation on the second file without referring to the history table.

11. A storage system comprising:
a memory device configured to store data and metadata of one or more files; and
a controller configured to control a data access operation of the memory device,
wherein the controller is further configured to perform a first deletion operation on a first file in response to a first deletion request from a host based on a secure deletion on the first file, the first deletion operation including invalidation of data of the first file and physical erasure of the invalid data of the first file, and
wherein after the physical erasing of the invalid data of the first file is complete, the controller is further configured to perform a second deletion operation on the first file in response to a second deletion request from the host based on the secure deletion on the first file, the second deletion operation is performed based on a control of an operating system (OS) of the host,
the controller is further configured to perform a third deletion operation on a second file based on a normal deletion on the second file, wherein the third deletion operation is performed based on the control of the OS of the host before erasure of invalid data of the second file is performed.

12. The storage system of claim 11 , wherein the first deletion request and the second deletion request are different requests from each other.

13. The storage system of claim 11 further comprising a history table configured to store information associated with invalid data of the one or more files,
wherein, when a request from the host corresponds to the first deletion request, the controller is further configured to perform the physical erasure of the invalid data of the first file by referring to the history table.

14. The storage system of claim 13 , wherein the controller is further configured to further erase invalid data of at least one other file than the first file by referring to the history table.

15. The storage system of claim 13 , wherein, when a request from the host corresponds to the second deletion request, the controller is further configured to erase invalid data of one file indicated by the host without referring to the history table.

16. The storage system of claim 11 , wherein, when a request from the host corresponds to the first deletion request, the controller is further configured to change a file name of the first file by changing the metadata of the first file.

17. An operating method of a controller, the operating method comprising:
receiving a first deletion request for a first file among a plurality of files from a host;
performing a first deletion operation on the first file in response to the first deletion request based on a secure deletion on the first file, the first deletion operation including invalidation of data of the first file and physical erasure of the invalid data of the first file;
receiving, after the first deletion operation is completed, a second deletion request for the first file from the host;
performing a second deletion operation on the first file in response to the second deletion request from the host based on the secure deletion on the first file, the second deletion operation is performed based on a control of an operating system (OS) of the host:
performing a third deletion operation on a second file based on a normal deletion on the second file, wherein the third deletion operation is performed based on the control of the OS of the host before erasure of invalid data of the second file is performed,
wherein the controller includes a history table storing information associated with invalid data of the plurality of files, and
wherein the physical erasure in response to the first deletion request is performed by referring to the history table.

18. The operating method of claim 17 further comprising:
erasing, when a request from the host corresponds to the first deletion request, invalid data of at least one other file than the first file by referring to the history table.

19. The operating method of claim 17 further comprising:
changing, when a request from the host corresponds to the first deletion request, a file name of the first file by changing metadata of the first file.

Assignees

• Samsung Electronics Co Ltd

Inventors

• Park Jin-Hwan
• Kim Chan-Sol
• Jung Myung-Jin
• Kim Ji-Soo
• Kim Kyung-Ho
• Kang Pil-Sung
• Choi Bong-Jun
• Yu Chae-Won
• Lee So-Jeong

Classifications

• G06F2212/7205

  Cleaning, compaction, garbage collection, erase control · CPC title

• G06F21/6218

  to a system of files or objects, e.g. local or distributed file system or database · CPC title

• G06F2221/2143

  Clearing memory, e.g. to prevent the data from being stolen · CPC title

• G06F3/0623

  in relation to content · CPC title

• G06F16/122

  using management policies (point-in-time backing up or restoration of persistent data G06F11/1446; file migration policies for HSM systems G06F16/185) · CPC title