File system creating and deleting apparatus and driving method thereof

• US 10,191,909 B2
• Filed: 03/01/2016
• Issued: 01/29/2019
• Est. Priority Date: 03/03/2015
• Status: Active Grant

• Current Assignee: Electronics and Telecommunications Research Institute
• Original Assignee: Electronics and Telecommunications Research Institute
• Inventors: Lee, Sang Min, Kim, Young Kyun, Kim, Hong Yeon
• Primary Examiner(s): Nguyen, Kim T
• Application Number:
  US15/057,312
• Publication Number:
  US 20160259801A1
• Time in Patent Office: 1,064 Days
• Field of Search: 707692
• CPC Class Codes: G06F 16/162 Delete operations erasing in storage systems G06F3/0652
• CPC Class Codes: G06F 16/1774 Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files
• CPC Class Codes: G06F 16/2308 Concurrency control transaction processing G06F9/466
• CPC Class Codes: G06F 16/2336 Pessimistic concurrency control approaches, e.g. locking or multiple versions without time stamps

Abstract

Provided herein is a filing system creating and deleting apparatus, comprising an available inode pool in which inodes are to be stored, a file system object creating processor creating an inode allocating request signal in response to a file system creating request from an external resource, an inode allocating processor allocating at least one of inodes stored in the available inode pool in response to the inode allocating request signal, a file system object deleting processor creating an inode deallocating request signal in response to a file system deleting request from the external resource, an inode deleting thread collecting inodes requested to be deleted corresponding to the file system deleting request, and an inode deallocating processor deallocating the inode requested to be deleted from the inode deleting thread, wherein a number of inodes stored in the available inode pool is limited to no more than a maximum inode number in the available inode pool, and the inode requested to be deleted creates and deletes a file system stored in the available inode pool when the number of inodes stored in the available inode pool is smaller than the maximum inode number in the available inode pool.

Claims

1. A filing system creating and deleting apparatus, comprising:

an available inode pool in which inodes are to be stored;

a file system object creating processor creating an inode allocating request signal in response to a file system creating request from an external resource;

an inode allocating processor allocating at least one of inodes stored in the available inode pool in response to the inode allocating request signal;

a file system object deleting processor creating an inode deallocating request signal in response to a file system deleting request from the external resource;

an inode deleting thread collecting inodes requested to be deleted corresponding to the file system deleting request; and

an inode deallocating processor deallocating the inode requested to be deleted from the inode deleting thread,

wherein a number of inodes stored in the available inode pool is limited to no more than a maximum inode number in the available inode pool, and the inode requested to be deleted creates and deletes a file system stored in the available inode pool when the number of inodes stored in the available inode pool is smaller than the maximum inode number in the available inode pool,

wherein a deleting inode list is stored in the inode deleting thread and the deleting inode list includes a deleting inode head and at least one deleting inode entry, and

the inode requested to be deleted is stored in the deleting inode entry when the number of inodes stored in the available inode pool is the maximum inode number in the available inode pool.

2. The filing system creating and deleting apparatus of claim 1, further comprising an inode table manager managing an inode table on the basis of a signal from the inode allocating processor or the inode deallocating processor.

3. The filing system creating and deleting apparatus of claim 1, wherein the available inode pool comprises:

a concurrency control lock controlling accesses from a plurality of processors;

the maximum inode number;

a number of inodes stored in the available inode pool; and

an array of inodes stored in the available inode pool.

4. The filing system creating and deleting apparatus of claim 1, wherein the deleting inode head comprises:

a concurrency control lock controlling accesses from a plurality of processors;

an expire period in which the deleting inode list maintains; and

a pointer including NEXT and PREV indicating one of deleting inode entries,

wherein the deleting inode entry comprises;

a pointer including the NEXT and the PREV indicating one of the deleting inode head or another deleting inode entry;

a creating time in which the deleting inode entry is created;

a maximum number of inodes to be stored in the deleting inode entry;

a number of inodes stored in the deleting inode entry; and

an array of inodes stored in the deleting inode entry.

5. The filing system creating and deleting apparatus of claim 4, wherein the deleting inode entry is deallocated when a difference between the creating time of the deleting inode entry and a current time is over an expire period of the deleting inode head.

6. The filing system creating and deleting apparatus of claim 1, wherein a transaction structure is transmitted from the inode deleting thread to an inode deallocating processor,

wherein the transaction structure comprises:

a maximum number of entries to be stored in the transaction structure;

a number of entries stored in the transaction structure; and

an array of entries stored in the transaction structure, and

wherein the transaction structure is transmitted and inodes requested to be deleted stored in the transaction structure are deallocated when the number of entries in the transaction structure is a maximum entry number in the transaction structure or a predetermined period has elapsed.

7. A driving method of a filing system creating and deleting apparatus including an available inode pool in which inodes are to be stored, the driving method, comprising:

allocating an inode in response to a file creating request from an external source; and

processing an inode requested to be deleted corresponding to a file deleting request from the external source, wherein the allocating of the inode is performed only when the file creating request is received from the external resource and includes allocating one of inodes stored in the available inode pool,

wherein the deleting of the inode is performed when the file deleting request is received from the external resource, and includes storing an inode requested to be deleted in the available inode pool,

wherein the filing system creating and deleting apparatus further comprises an inode deleting thread including a deleting inode head and at least one deleting inode entry, inodes are to be stored in the deleting inode entry,

the processing of the inode requested to be deleted further comprises storing the inode requested to be deleted in the deleting inode entry,

the inode requested to be deleted is stored in the available inode pool when a number of inodes stored in the available inode pool is smaller than a maximum inode number in the available inode pool, and

the inode requested to be deleted is stored in the deleting inode entry is performed when the number of inodes stored in the available inode pool is the maximum inode number in the available inode pool.

8. The driving method of claim 7, wherein the deleting inode head includes an expire period in which the deleting inode list maintains,

the deleting inode entry includes a creating time in which the deleting inode entry is created and an array of inodes stored in the deleting inode entry,

the driving method of the filing system creating and deleting apparatus further comprises processing the deleting inode entry,

the processing of the deleting inode entry includes comparing a difference between a current time and the creating time with the expire period and deallocating the deleting inode entry, and

the deallocating of the deleting inode entry is performed when the difference is greater than the expire period.

9. The driving method of claim 8, wherein the inode deleting thread transmits a transaction structure to an inode deallocating processor,

the transaction structure includes a maximum number of entries to be stored in the transaction structure, a number of entries stored in the transaction structure and an array of entries stored in the transaction structure,

the processing of the deleting inode entry includes comparing the maximum number of entries stored in the transaction structure and the number of entries stored in the transaction structure, and

the transaction structure is transmitted to the inode deallocating processor when the number of entries stored in the transaction structure is the maximum number of entries stored in the transaction structure.

10. The driving method of claim 9, further comprising deallocating the available inode pool, the deleting inode entry and the transaction structure,

the deallocating of the available inode pool, the deleting inode entry and the transaction structure is performed only when a system completing request is received from an external source, and

in the deallocating of the available inode pool, the deleting inode entry and the transaction structure, inodes stored in the available inode pool, inodes stored in the deleting inode entry and entries stored in the transaction structure are deleted.

11. The driving method of claim 9, wherein the deallocating of the deleting inode entry comprises adding the deleting inode entry to the transaction structure and inserting inode stored in the deleting inode entry into the available inode pool, and

the adding of the deleting inode entry to the transaction structure is performed only when the inserting inode stored in the deleting inode entry into the available inode pool fails.