Apparatus and method for hardware-based file system

• US 8,224,877 B2
• Filed: 08/20/2007
• Issued: 07/17/2012
• Est. Priority Date: 11/01/2002
• Status: Active Grant

• Current Assignee: Hitachi Vantara, LLC (Hitachi, Ltd.)
• Original Assignee: Bluearc UK Ltd. (Hitachi, Ltd.)
• Inventors: Barrall, Geoffrey S., Benham, Simon L., Willis, Trevor E., Aston, Christopher J.
• Primary Examiner(s): Wu, Yicun
• Application Number:
  US11/841,353
• Publication Number:
  US 20080040385A1
• Time in Patent Office: 1,793 Days
• Field of Search: 707821-831
• US Class Current: 707/821
• CPC Class Codes: G06F 12/0246 in block erasable memory, e.g. flash memory
• CPC Class Codes: G06F 16/128 Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion use of snapshots for error detection or correction G06F11/14, G06F11/16
• CPC Class Codes: G06F 16/183 Provision of network file services by network file servers, e.g. by using NFS, CIFS network file access protocols H04L67/1097
• CPC Class Codes: G06F 16/1873 Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

A hardware-based file system includes multiple linked sub-modules that perform functions ancillary to client data handling. Each sub-module is associated with a metadata cache. A doubly-rooted structure is used to store each file system object at successive checkpoints. Metadata is stored within an object and/or as a separate object. Provisions are made for allocating sparse objects. A delayed write feature is used for writing certain objects into non-volatile storage. Checkpoints can be retained as read-only versions of the file system. Modifications to the file system are accomplished without affecting the contents of retained checkpoints. The file system can be reverted to a retained checkpoint. Multiple file servers can be interconnected as a cluster, and each file server stores requests from another file server. Interconnections between file servers can be dynamically modified. A distributed locking mechanism is used to control access to file system objects stored by the file servers.

Claims

1. A method for maintaining a file system object in a non-volatile storage device at successive checkpoints, the method comprising:

maintaining an object structure in a memory for the file system object, the object structure comprising a first tree structure rooted by a first root node and a second tree structure rooted by a second root node, each tree structure optionally including a number of intermediate nodes and a number of data blocks, each tree structure representing a version of the file system object; and

alternately managing changes to the file system object using the first tree structure rooted by the first root node while storing the second tree structure rooted by the second root node in the non-volatile storage device for a checkpoint that is used for keeping the consistency of data on the non-volatile storage device if the contents of the memory are lost and managing changes to the object structure using the second tree structure rooted by the second root node while storing the first tree structure rooted by the first root node in the non-volatile storage device for a subsequent checkpoint.

2. The method of claim 1, further comprising:

maintaining a version number for each root node, the version number indicating the checkpoint associated with the corresponding tree structure.

3. The method of claim 1, wherein the non-volatile storage device comprises a plurality of sectors, and wherein the first and second root nodes are stored in adjacent sectors in the non-volatile storage.

4. The method of claim 2, further comprising:

determining a latest valid version of the file system object based upon the version numbers of the root nodes.

5. The method of claim 1, further comprising:

maintaining a list of free space areas of the non-volatile storage device;

maintaining a list of free root nodes;

allocating the root nodes for the object structure from one of the list of free space areas and the list of free root nodes; and

allocating intermediate nodes and data blocks for the object structure only from the list of free space areas.

6. The method of claim 5, further comprising:

deleting the file system object from the non-volatile storage device.

7. The method of claim 6, wherein deleting the file system object from the non-volatile storage device comprises:

adding the root nodes to the list of free root nodes; and

adding the intermediate nodes and data blocks to the list of free space areas.

8. An apparatus comprising:

a non-volatile storage device;

means for maintaining an object structure in a memory for the file system object, the object structure comprising a first tree structure rooted by a first root node and a second tree structure rooted by a second root node, each tree structure optionally including a number of intermediate nodes and a number of data blocks, each tree structure representing a version of the file system object; and

means for alternately managing changes to the file system object using the first tree structure rooted by the first root node while storing the second tree structure rooted by the second root node in the non-volatile storage device for a checkpoint that is used for keeping the consistency of data on the non-volatile storage device if the contents of the memory are lost and managing changes to the object structure using the second tree structure rooted by the second root node while storing the first tree structure rooted by the first root node in the non-volatile storage device for a subsequent checkpoint.

9. The apparatus of claim 8, further comprising:

means for retaining read-only versions of the object using the object structure.

10. The apparatus of claim 9, further comprising:

means for deleting a retained read-only version of the object from the object structure.

11. The apparatus of claim 9, further comprising:

means for deleting the current version of the object while at least one retained read-only version of the object exists in the object structure.

12. The apparatus of claim 9, further comprising:

means for reverting the current version of the object to a retained read-only version of the object.

13. Apparatus comprising:

a non-volatile storage device; and

a storage processor configured to maintain an object structure in a memory for a file system object, the object structure comprising a first tree structure rooted by a first root node and a second tree structure rooted by a second root node, each tree structure optionally including a number of intermediate nodes and a number of data blocks, each tree structure representing a version of the file system object, the storage processor further configured to alternately manage changes to the file system object using the first tree structure rooted by the first root node while storing the second tree structure rooted by the second root node in the non-volatile storage device for a checkpoint that is used for keeping the consistency of data on the non-volatile storage device if the contents of the memory are lost and manage changes to the object structure using the second tree structure rooted by the second root node while storing the first tree structure rooted by the first root node in the non-volatile storage device for a subsequent checkpoint.

14. The apparatus of claim 13, wherein the storage processor is hardware-implemented.

15. The apparatus of claim 13, wherein the storage processor is hardware-accelerated.

16. The apparatus of claim 13, wherein the storage processor includes a plurality of linked sub-modules including an object store sub-module configured to perform at least one maintaining the object structure and alternately managing the object using the first and second tree structures.

17. The apparatus of claim 16, wherein the object store sub-module is hardware-implemented.

18. The apparatus of claim 16, wherein the object store sub-module is hardware-accelerated.