System and method for managing filesystem objects

• US 9,317,511 B2
• Filed: 06/19/2012
• Issued: 04/19/2016
• Est. Priority Date: 06/19/2012
• Status: Active Grant

• Current Assignee: Infinidat Ltd.
• Original Assignee: Infinidat Ltd.
• Inventors: Kanfi, Arnon
• Primary Examiner(s): Le, Miranda
• Application Number:
  US13/526,572
• Publication Number:
  US 20130339406A1
• Time in Patent Office: 1,400 Days
• Field of Search: 707/822, 707/825, 707/828, 707/829, 707/830, 707/999.2
• US Class Current: 1/1
• CPC Class Codes: G06F 16/122 using management policies backup systems G06F11/1446; file migration policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/185 Hierarchical storage management [HSM] systems, e.g. file migration or policies thereof details of archiving G06F16/11
• CPC Class Codes: G06F 16/289 Object oriented databases

Abstract

A system and method of operating a filesystem for managing filesystem objects is disclosed. The filesystem objects are characterized by metadata parameters included in a global directory object arranged in a plurality of global directory object (GDO) pages. Responsive to receiving a request for creating a new filesystem object, a parent key is obtained. The parent key is indicative of an identifier of a direct parent directory requested for hosting the new filesystem object. A target page that corresponds to the parent key is located within the plurality of GDO pages. The target page further includes a direct parent directory metadata record associated with the direct parent key and includes metadata parameters related to the direct parent directory. An object key is created as corresponding to the same target page, thereby enabling accommodation of an object metadata record, related to the new filesystem object, on the target page.

Claims

1. A method for managing filesystem objects of a filesystem, the method comprising:

receiving a request for creating a new file;

obtaining, in response to the receiving of the request for creating the new file, a direct parent object key that identifies a direct parent directory requested for hosting said new file;

locating within a plurality of global directory object (GDO) pages of a GDO a target page by looking up the GDO with said direct parent object key, wherein said target page comprises a direct parent directory metadata record that is (i) associated with the direct parent object key and (ii) comprises metadata parameters related to the direct parent directory;

wherein the filesystem objects are (i) selected from files and directories, (ii) located in a non-transitory storage media, (iii) arranged in a hierarchical directory structure, and (iv) associated with a plurality of metadata records;

wherein the plurality of metadata records are included in the GDO;

creating an object key for identifying the new file in the filesystem and for looking up the new file in the GDO, wherein said object key is created as having a value that corresponds to a lexicographical order of object keys associated with metadata records of the plurality of metadata records that are included in the target page, thereby enabling accommodation of an object metadata record on said target page, said object metadata record associated with the object key for identifying the new file and configured to comprise metadata parameters related to the new file;

wherein the plurality of metadata records are ordered within the GDO by values of object keys identifying the filesystem objects;

in response to receiving a request for creating a new sub-directory under the direct parent directory, creating an object directory identifier, such that the object directory identifier is lexicographically subsequent to a direct parent directory identifier of the direct parent directory,

wherein one of the following is true;

(i) the object directory identifier comprises the direct parent directory identifier as a most significant part, appended by an uniquifier index; and

(ii) the object directory identifier is selected from a predefined pool of consecutive identifiers, said predefined pool being associated with the target page; and

creating a filename value by applying a formula on an object name comprised in said request for creating the new file, wherein the object key comprises a direct parent directory identifier uniquely identifying the direct parent directory, as a most significant part of the object key and a respective filename value as a least significant part of the object key.

2. The method of claim 1, comprising generating said object metadata record file;

associating said object metadata record with the object key, and storing said object metadata record on the target page.

3. The method of claim 1, wherein said request for creating the new file comprises a parent key, wherein said parent key is indicative of a non-direct parent directory, and wherein the method further comprising:

a. locating within the plurality of GDO pages a page, by looking up the GDO with said parent key, wherein said page comprises a non-direct parent metadata record associated with the non-direct parent directory;

b. obtaining a respective directory identifier and a filename, corresponding to the non-direct parent directory, from the non-direct parent metadata record;

c. composing a new parent key based on the directory identifier and the filename and repeating the locating and the obtaining until composing the direct parent key.

4. The method of claim 1, wherein the object directory identifier comprises the direct parent directory identifier as the most significant part, appended by the uniquifier index.

5. The method of claim 1, wherein the object directory identifier is selected from the predefined pool of consecutive identifiers, said predefined pool being associated with the target page.

6. The method of claim 1, wherein the filename value is created such that multiple filename values are consecutive if corresponding object names are consecutive.

7. The method of claim 1 further comprising creating a file handle configured to accommodate the object key and providing the file handle in response to said request for creating the new file.

13. The method of claim 1, wherein the value of the object key is lexicographically subsequent to a value of the direct parent object key.

8. A system for managing filesystem objects of a filesystem, the system comprising a processor and a metadata cache memory in communication with the processor, for caching global directory object (GDO) pages of a GDO

wherein the filesystem objects are (i) selected from files and directories, (ii) located in a non-transitory storage media, (iii) arranged in a hierarchical directory structure, and (iv) associated with a plurality of metadata records;

wherein the plurality of metadata records are included in the GDO;

wherein, in response to receiving a request for creating a new file, said processor is configured to;

obtain a direct parent object key identifying a direct parent directory requested for hosting said new file;

locate within the plurality of GDO pages a target page by looking up the GDO with said direct parent object key, wherein said target page comprises a direct parent directory metadata record associated with the direct parent object key and comprising metadata parameters related to the direct parent directory;

create an object key for identifying the new file in the filesystem and for looking up the new file in the GDO, wherein said object key is created as having a value that corresponds to a lexicographical order of object keys associated with metadata records, of the plurality of metadata records, comprised in the target page, thereby enabling accommodation of an object metadata record on said target page, said object metadata record associated with the object key and configured to comprise metadata parameters related to the new file;

wherein the plurality of metadata records are ordered within the GDO by values of object keys identifying the filesystem objects;

in response to receiving a request for creating a new sub-directory under the direct parent directory, said processor is configured to create an object directory identifier, such that the object directory identifier is lexicographically subsequent to a direct parent directory identifier of the direct parent directory;

wherein one of the following is true;

(i) the object directory identifier comprises the direct parent directory identifier as a most significant part, appended by an uniquifier index; and

(iii) the object directory identifier is selected from a predefined pool of consecutive identifiers, said predefined pool being associated with the target page; and

creating a filename value by applying a formula on an object name comprised in said request for creating the new file, wherein the object key comprises a direct parent directory identifier uniquely identifying the direct parent directory, as a most significant part of the object key and a respective filename value as a least significant part of the object key.

9. The system of claim 8, wherein said request for creating the new files comprises a parent key, wherein said parent key is indicative of a non-direct parent directory, and wherein said processor is further configured to:

a. locate within the plurality of GDO pages a page, by looking up the GDO with said parent key, wherein said page comprises a non-direct parent metadata record associated with a non-direct parent directory;

b. obtain a respective directory identifier and a filename from the non-direct parent metadata record;

c. compose a new parent key based on the directory identifier and the filename and repeat operations a) and b) until composing the direct parent key.

10. The system of claim 8, wherein the object directory identifier comprises the direct parent directory identifier as the most significant part, appended by the uniquifier index.

11. The system of claim 8, wherein the object directory identifier is selected from the predefined pool of consecutive identifiers, said predefined pool associated with the target page.

12. The system of claim 8 wherein the filesystem objects are stored in a separate storage system operatively connected to the system.

14. The system of claim 8, wherein the value of the object key is lexicographically subsequent to a value of the direct parent object key.