System and method for caching network file systems

• US 9,152,600 B2
• Filed: 07/18/2013
• Issued: 10/06/2015
• Est. Priority Date: 04/25/2005
• Status: Active Grant

• Current Assignee: NetApp, Inc.
• Original Assignee: NetApp, Inc.
• Inventors: Lango, Jason Ansel, English, Robert M., Eastham, Paul Christopher, Zheng, Qinghua, Quirion, Brian Mederic, Griess, Peter, Amdur, Matthew Benjamin, Ayyar, Kartik, Tsai, Robert Lieh-Yuan, Grunwald, David, Wagner, J. Chris, Ackaouy, Emmanuel, Prakash, Ashish
• Primary Examiner(s): NGUYEN, THU HA T
• Application Number:
  US13/945,637
• Publication Number:
  US 20130304844A1
• Time in Patent Office: 810 Days
• Field of Search: 709/203, 709/204, 709/214, 709/216, 709/217, 711/118, 711/119, 711/120
• US Class Current: 1/1
• CPC Class Codes: G06F 15/167 using a common memory, e.g. mailbox
• CPC Class Codes: G06F 2003/0697 device management, e.g. handlers, drivers, I/O schedulers
• CPC Class Codes: G06F 3/0601 Interfaces specially adapted for storage systems
• CPC Class Codes: G06F 3/0617 in relation to availability
• CPC Class Codes: G06F 3/0643 Management of files
• CPC Class Codes: G06F 3/0665 at area level, e.g. provisioning of virtual or logical volumes
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 3/0689 Disk arrays, e.g. RAID, JBOD
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/59 Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable

Abstract

A network caching system has a multi-protocol caching filer coupled to an origin server to provide storage virtualization of data served by the filer in response to data access requests issued by multi-protocol clients over a computer network. The multi-protocol caching filer includes a file system configured to manage a sparse volume that “virtualizes” a storage space of the data to thereby provide a cache function that enables access to data by the multi-protocol clients. To that end, the caching filer further includes a multi-protocol engine configured to translate the multi-protocol client data access requests into generic file system primitive operations executable by both the caching filer and the origin server.

Claims

1. A caching system, comprising:

a plurality of network interfaces configured to communicate data over a computer network, wherein a first network interface is connected to a client and a second network interface is connected to an origin computer;

a processor coupled to the plurality of network interfaces and configured to execute one or more processes; and

a memory configured to store a process executable by the processor, the process when executed operable to;

receive a data access request from the client for the data;

send a request to the origin computer for attributes associated with the data;

service the data access request at the caching system in response to determining that the requested attributes from the origin computer do not differ from local attributes associated with the data stored at the caching system; and

retrieve the data and the requested attributes from the origin computer and verify that the requested attributes have not changed since the data was retrieved from the origin computer, in response to determining that the requested attributes differ from the local attributes.

2. The caching system of claim 1, wherein the process when executed is further operable to:

determine that the requested attributes have changed since the data was retrieved from the origin computer; and

retrieve updated data and updated attributes from the origin computer in response to determining that the requested attributes have changed since the data was retrieved from the origin computer.

3. The caching system of claim 1, wherein the process when executed is further operable to:

utilize a sparse volume of the caching system, wherein the sparse volume includes at least one absent block representing missing data that is missing from the sparse volume, wherein the missing data of the absent block is stored on the origin computer and retrieved in a manner that is transparent to the client.

4. The caching system of claim 1, wherein the process when executed is further operable to:

examine at least one of an access time and a modification time of an inode associated with the local attributes to determine whether the requested attributes differ from local attributes.

5. The caching system of claim 3, wherein the process when executed is further operable to:

utilize a remote update engine (RUE) to forward any file system operations that modify the sparse volume to the origin computer of the caching system.

6. The caching system of claim 3, wherein the process when executed is further operable to:

utilize a truncator to implement a cache ejection policy to reclaim storage space if the sparse volume becomes full.

7. The caching system of claim 1, wherein the process when executed is further operable to:

determine whether the data is located at the caching system;

send the data to the client in response to determining that the data is located at the caching system; and

acquire the data from the origin computer and send the data to the client in response to determining that the data is not located at the caching system.

8. The caching system of claim 1, wherein the requested attributes include at least one of a modification time, a number of links, and a creation time.

9. The caching system of claim 1, wherein determining that the requested attributes differ from local attributes indicates that the data has been modified since it was last cached at the caching system.

10. A method comprising;

receiving, at a caching computer, a data access request from a client for data, wherein the caching computer is coupled to the client and an origin computer over a computer network;

sending a request for attributes associated with the data from the caching computer to the origin computer;

in response to determining, by a processor of the caching computer, that the requested attributes from the origin computer do not differ from local attributes associated with the data stored at the caching computer, servicing the data access request at the caching computer; and

in response to determining, by the processor of the caching computer, that the requested attributes from the origin computer differ from the local attributes;

retrieving the data and the requested attributes from the origin computer,

and

verifying that the requested attributes have not changed since the data was retrieved from the origin computer.

11. The method of claim 10, further comprising:

retrieving updated data and updated attributes in response to determining that the requested attributes have changed since the data was retrieved from the origin computer.

12. The method of claim 10, further comprising:

utilizing a sparse volume at the caching computer, wherein the sparse volume includes at least one absent block representing missing data that is missing from the sparse volume, wherein the missing data of the absent block is stored on the origin computer and retrieved in a manner that is transparent to the client.

13. The method of claim 10, further comprising:

examining at least one of an access time and a modification time of an inode associated with the local attributes to determine whether the requested attributes differ from local attributes.

14. The method of claim 12, further comprising:

utilize a remote update engine (RUE) to forward any file system operations that modify the sparse volume to the origin computer of the caching computer.

15. The method of claim 12, further comprising:

utilize a truncator to implement a cache ejection policy to reclaim storage space if the sparse volume becomes full.

16. The method of claim 10, further comprising:

determining whether the data is located at the caching computer;

sending the data to the client in response to determining that the data is located at the caching computer; and

acquiring the data from the origin computer and sending the data to the client in response to determining that the data is not located at the caching computer.

17. The method of claim 10, wherein the requested attributes include at least one of a modification time, a number of links, and a creation time.

18. The method of claim 10, wherein determining that the requested attributes differ from local attributes indicates that the data has been modified since it was last cached at the caching computer.

19. A non-transitory computer-readable storage medium containing executable program instructions executed by a processor, comprising:

program instructions that receive a data access request from a client for data, wherein the request is received at a caching computer that is coupled to the client and an origin computer over a computer network;

program instructions that send a request for attributes associated with the data from the caching computer to the origin computer;

program instructions that service the data access request at the caching computer in response to determining that the requested attributes from the origin computer do not differ from local attributes associated with the data stored at the caching computer; and

program instructions that retrieve the data and the requested attributes from the origin computer and verify that the requested attributes have not changed since the data was retrieved from the origin computer, in response to determining that the requested attributes differ from the local attributes.