Mechanism for handling file level and block level remote file accesses using the same server

• US 6,868,417 B2
• Filed: 12/18/2000
• Issued: 03/15/2005
• Est. Priority Date: 12/18/2000
• Status: Expired due to Term

• Current Assignee: NetApp, Inc.
• Original Assignee: Spinnaker Networks, Inc. (NetApp, Inc.)
• Inventors: Kazar, Michael L., Sanzi, Richard N. Jr.
• Primary Examiner(s): Amsbury, Wayne
• Assistant Examiner(s): Nguyen, Cindy
• Application Number:
  US09/740,160
• Publication Number:
  US 20020112022A1
• Time in Patent Office: 1,548 Days
• Field of Search: 707/106, 707/1, 707/200, 709/214, 711/148, 711/170
• US Class Current: 1/1
• CPC Class Codes: G06F 16/148 File search processing
• CPC Class Codes: G06F 16/174 Redundancy elimination performed by the file system management of the data involved in backup or backup restore using de-duplication of the data G06F11/14
• CPC Class Codes: G06F 16/1824 implemented using Network-attached Storage [NAS] architecture distributed or networked storage systems G06F3/067; protocols for distributed storage of data in a network H04L67/1097
• CPC Class Codes: Y10S 707/99931 Database or file accessing

Abstract

An apparatus for handling file level and block level remote file accesses. The apparatus includes a block level server. The apparatus includes a file level server. The apparatus includes a storage layer implementing an inode layer performing inode operations, and storing data accessed by the file level and block level servers. The apparatus includes a management layer connected to the storage layer underlying the block and file level servers, which performs data management operations upon the underlying data. A method of handling file level and block level network file accesses. The method includes the steps of performing management operations by a management layer for a block level server and a file level server. Then there is the step of performing the servers'"'"' data accessing and updating operations using a vnode layer implemented on top of an inode layer. Then there is the step of storing data from the block level server or the file level server in a storage layer connected to the management layer.

Claims

1. An apparatus for handling file level and block level remote file accesses comprising:

a block level server for serving block level data;

a file level server for serving file level data and combined with the block level server;

a storage layer implementing an mode layer performing mode operations, and storing data accessed by the file level and block level servers, the block level server and the file level server sharing the storage layer, the block level server providing service through implementation in terms of the mode layer operations; and

a management layer connected to the storage layer underlying the block and file level servers, which performs identical data management operations upon the underlying block level and file level data from either the block level server or the file level server, respectively.

2. An apparatus as described in claim 1 wherein the block level sever includes a SAN server exporting data via SCSI over fibrechannel or SCSI over IP protocols.

3. An apparatus as described in claim 2 wherein the file level server includes a NAS server.

4. An apparatus as described in claim 3 wherein the management layer implements point in time copies, read-only replication, dynamic data relocation or disk space virtualization operations on top of the mode operations performed by the underlying storage layer.

5. An apparatus as described in claim 4 wherein the file level server includes a vnode operations layer.

6. An apparatus as described in claim 5 wherein the management layer uses space-saving copy-on-write operations provided by the storage layer when processing management requests from the associated NAS or SAN servers.

7. An apparatus as described in claim 6 wherein the vnode operations layer uses space-saving copy-on-write operations provided by the storage layer when processing system requests from the associated NAS or SAN servers.

8. An apparatus as described in claim 7 wherein the vnode operations layer implements a file system tree of files and directories out of a linear space of modes provided by the storage layer.

9. An apparatus as described in claim 8 wherein the vnode operations layer implemented on top of the mode layer includes at least an mode storing all modes within the file system, and an mode storing the file system'"'"'s root directory.

10. An apparatus as described in claim 9 wherein an inode points to data blocks, directly or indirectly, and the copy-on-write management operations create cloned modes having pointers that point to the same data blocks.

11. An apparatus as described in claim 10 wherein pointers to data blocks or indirect blocks contain a copy-tree-on-write bit which indicates whether the respective block pointed to by the pointer is also pointed to by another clone mode, the bit being used to determine when to free the respective data blocks when deleting a file, and to determine when to copy the respective data blocks when updating a file;

if the block with the bit set points to an indirect block, all blocks pointed to directly or indirectly by that indirect block are treated as if their pointers have the bit set as well.

18. An apparatus as described in claim 1 including a partition having a physical space in which the block level server and the file level server exist.

12. A method of handling file level and block level network file accesses comprising the steps of:

performing identical management operations on data from either a block level server or a file level server combined with the block level server by a management layer for the block level server and the file level server;

performing the servers'"'"' data accessing and updating operations using a vnode layer implemented on top of an mode layer; and

storing data from the block level server or the file level server in a storage layer for the data from either the block level server or the file level server connected to the management layer, the block level server providing service through implementation in terms of operations by the mode layer.

13. A method as described in claim 12 wherein the performing step includes the step of performing space saving copy-on-write operations using an mode operations layer accessed by the data management layer on data from a NAS or SAN server.

14. A method as described in claim 13 wherein the performing step includes the step of implementing, in a vnode layer, a tree of files and directories on top of a linear array of modes.

15. A method as described in claim 14 wherein the performing step includes the steps of performing copy-on-write operations with the inode operations layer whenever a cloned mode is updated by a file or block level operation.

16. A method as described in claim 15 wherein the performing step includes the step of creating a clone of an mode sharing all data and indirect blocks, using the mode operations layer.

17. A method as described in claim 16 wherein the performing step includes the step of freeing the respective data and indirect blocks when deleting a file from a volume when the copy-tree-on-write bit is clear on one or more of the blocks of the file.

19. A method as described in claim 12 including a partition having a physical space in which the block level server and the file level server exist.