Method and system for managing shrinking inode file space consumption using file trim operations
US-2017262463-A1 · Sep 14, 2017 · US
US10983709B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10983709-B2 |
| Application number | US-202016777346-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 30, 2020 |
| Priority date | May 27, 2016 |
| Publication date | Apr 20, 2021 |
| Grant date | Apr 20, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Methods, non-transitory computer readable media, and computing devices that execute a storage operation, without journaling the storage operation in a log, and withhold from a file system a list of freed inodes including an indication of an inode freed as a result of the execution of the storage operation. A consistency point operation is then initiated that retrieves storage operations logged as journal entries in the log and commits a result of each of the storage operations to data storage devices. A list of available inodes is updated based on the list of freed inodes, when the consistency point operation is determined to be complete. This technology reduces the number of storage operations that are required to be journaled to maintain consistency of a file system, thereby reducing the runtime resources required to facilitate the journaling and replay resource required to replay the storage operations following a recovery.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: selecting, by a computing device, a subset of received storage operations for journaling based on one or more types of the received storage operations and logging the subset of the received storage operations as journal entries in a log; executing, by the computing device, an unselected one of the received storage operations, without journaling the unselected one of the received storage operations in the log, and withholding from a file system a list of freed inodes comprising an indication of an inode freed as a result of the execution of the unselected one of the received storage operations; initiating, by the computing device, a consistency point operation that retrieves the subset of the received storage operations logged as journal entries in the log and commits a result of each of the subset of the received storage operations to one or more data storage devices; and updating, by the computing device, a list of available inodes based on the list of freed inodes, when the consistency point operation is determined to be complete based on the log being cleared after the results of the subset of the received storage operations in the journal entries are committed to the one or more data storage devices. 2. The method of claim 1 , wherein the list of available inodes is accessible to the file system for use in inode assignment when storing new files. 3. The method of claim 1 , wherein the freed inode is associated with a deleted file that was stored in the file system, and on one or more of the data storage devices, before being deleted by the unselected one of the received storage operations. 4. The method of claim 1 , further comprising updating, by the computing device, the list of available inodes to include the indication of the freed Mode and one or more other inodes freed during the consistency point operation. 5. The method of claim 1 , further comprising clearing, by the computing device, the list of freed inodes, when the consistency point operation is determined to be complete based on the log being cleared after the results of the subset of the received storage operations in the journal entries are committed to the one or more data storage devices. 6. The method of claim 1 , wherein the unselected one of the received storage operations is executed prior to initiation of the consistency point operation. 7. A non-transitory machine readable medium having stored thereon instructions for improved journal performance in a storage network comprising machine executable code which when executed by at least one machine causes the machine to: select a subset of received storage operations for journaling based on one or more types of the received storage operations and log the subset of the received storage operations as journal entries in a log; execute an unselected one of the received storage operations, without journaling the unselected one of the received storage operations in the log, and withhold from a file system a list of freed inodes comprising an indication of an inode freed as a result of the execution of the unselected one of the received storage operations; initiate a consistency point operation that retrieves the subset of the received storage operations logged as journal entries in the log and commits a result of each of the subset of the received storage operations to one or more data storage devices; and update a list of available inodes based on the list of freed inodes, when the consistency point operation is determined to be complete. 8. The non-transitory machine readable medium of claim 7 , wherein the list of available inodes is accessible to the file system for use in inode assignment when storing new files. 9. The non-transitory machine readable medium of claim 7 , wherein the freed inode is associated with a deleted file that was stored in the file system, and on one or more of the data storage devices, before being deleted by the unselected one of the received storage operations. 10. The non-transitory machine readable medium of claim 7 , wherein the machine executable code when executed by the machine further causes the machine to update the list of available inodes to include the indication of the freed inode and one or more other inodes freed during the consistency point operation. 11. The non-transitory machine readable medium of claim 7 , wherein the machine executable code when executed by the machine further causes the machine to clear the list of freed inodes, when the consistency point operation is determined to be complete. 12. The non-transitory machine readable medium of claim 7 , wherein the unselected one of the received storage operations is executed prior to initiation of the consistency point operation. 13. The non-transitory machine readable medium of claim 7 , wherein the consistency point operation is determined to be complete based on the log being cleared after the results of the subset of the received storage operations in the journal entries are committed to the one or more data storage devices. 14. A computing device, comprising: a memory containing machine readable medium comprising machine executable code having stored thereon instructions for improved journal performance in a storage network; and a processor coupled to the memory, the processor configured to execute the machine executable code to cause the processor to: select a subset of received storage operations for journaling based on one or more types of the received storage operations and log the subset of the received storage operations as journal entries in a log; execute an unselected one of the received storage operations, without journaling the unselected one of the received storage operations in the log, and withhold from a file system a list of freed inodes comprising an indication of an inode freed as a result of the execution of the unselected one of the received storage operations; initiate a consistency point operation; and update a list of available inodes based on the list of freed inodes, when the consistency point operation is determined to be complete based on the log being cleared after the results of the subset of the received storage operations in the journal entries are committed to the one or more data storage devices. 15. The computing device of claim 14 , wherein the list of available inodes is accessible to the file system for use in inode assignment when storing new files. 16. The computing device of claim 14 , wherein the freed inode is associated with a deleted file that was stored in the file system, and on one or more of the data storage devices, before being deleted by the unselected one of the received storage operations. 17. The computing device of claim 14 , wherein the processor is further configured to execute the machine executable code to further cause the processor to update the list of available inodes to include the indication of the freed inode and one or more other inodes freed during the consistency point operation. 18. The computing device of claim 14 , wherein the processor is further configured to execute the machine executable code to further cause the processor to clear the list of freed inodes, when the consistency point operation is determined to be complete based on the log being cleared after the results of the subset of the received storage operations in the journal entries are committed to the one or more data storage devices. 19. The computing device of claim 14 , wherein the unselected one of the received storage operatio
in relation to data integrity, e.g. data losses, bit errors · CPC title
Replication mechanisms · CPC title
Non-volatile semiconductor memory arrays · CPC title
Command handling arrangements, e.g. command buffers, queues, command scheduling · CPC title
Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.