Method and system for responding to file system requests

• US 8,032,697 B2
• Filed: 06/26/2009
• Issued: 10/04/2011
• Est. Priority Date: 12/07/2000
• Status: Expired due to Fees

• Current Assignee: NetApp, Inc.
• Original Assignee: NetApp, Inc.
• Inventors: Bianchini, Ronald P. Jr., Kazar, Michael L., Gohh, Fred, Nydick, Daniel S., Speiser, Benjamin, Sanzi, Richard N. Jr.
• Primary Examiner(s): PEUGH, BRIAN R
• Application Number:
  US12/459,043
• Publication Number:
  US 20090271459A1
• Time in Patent Office: 830 Days
• Field of Search: None
• US Class Current: 711/112
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06
• CPC Class Codes: G06F 16/148 File search processing
• CPC Class Codes: G06F 16/16 File or folder operations, e.g. details of user interfaces specifically adapted to file systems
• 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: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

A system for responding to file system requests having file IDs comprising V, a volume identifier specifying the file system being accessed, and R, an integer, specifying the file within the file system being accessed. The system includes D disk elements in which files are stored, where D is greater than or equal to 1 and is an integer. The system includes a switching fabric connected to the D disk elements to route requests to a corresponding disk element. The system includes N network elements connected to the switching fabric. Each network element has a mapping function that for every value of V, specifies one or more elements from the set D that store the data specified by volume V, where N is greater than or equal to 1 and is an integer and N+D is greater than or equal to 3, which receives the requests and causes the switching fabric to route the requests by their file ID according to the mapping function.

Claims

1. A system for responding to file system requests having file IDs comprising V, a volume identifier specifying the file system being accessed, and R, an integer, specifying the file within the file system being accessed comprising:

D disk elements in which files are stored, where D is greater than or equal to 2 and is an integer;

a switching fabric having a first switching element and a second switching element, each of which are connected to each of the D disk elements to route requests to a corresponding disk element based on the file system request'"'"'s ID; and

N network elements, each of which is connected to each of the switching elements of the switching fabric, each network element having a mapping function that for every value of V, specifies one or more elements from the set D that store the data specified by volume V, where N is greater than or equal to 2 and is an integer and N +D is greater than or equal to 4, which receives the requests and causes either the first or second switching element of the switching fabric to route the requests by their file ID according to the mapping function, the switching fabric connected between the disk elements and the network elements, the disk elements form a cluster, with one of the disk elements being a cluster coordinator which communicates with each disk element in the cluster to collect from and distribute to the network elements which file systems are stored in each disk element of the cluster at predetermined times.

2. A system as described in claim 1 wherein the cluster coordinator determines if each disk element is operating properly and redistributes requests for any disk element that is not operating properly;

and allocates virtual network interfaces to network elements and assigns responsibility for the virtual network interfaces to network elements for a failed network element.

3. A system as described in claim 2 wherein network elements and disk elements can be added dynamically.

4. A system as described in claim 3 wherein each network element advertises the virtual interfaces it supports to all disk elements.

5. A system as described in claim 4 wherein each network element includes a translator which obtains file IDs from path names included in individual file system requests.

6. A system as described in claim 5 wherein each disk element and each network element has a file system location database which maintains a mapping from all file system identifiers V to disk element identifiers so each network element can translate each file system request ID into a corresponding disk element location.

7. A system as described in claim 6 wherein each disk element and each network element has a controller, and each disk element controller communicates with the network element controllers to identify which files are stored at the respective disk element.

8. A system as described in claim 7 wherein each network element can respond to any request for any disk element.

9. A system as described in claim 8 wherein each network element has a network port through which requests are received by the respective network element wherein all the network elements and disk elements together appear as a single system that can respond to any request at any network port of any network element.

10. A system as described in claim 9 wherein each disk element has all files with the same file system ID for one or more values of V.

11. A system as described in claim 10 wherein each request has an active disk element and a passive disk element associated with each request, wherein if the active disk element fails, the passive disk element is used to respond to the request.

12. A system as described in claim 11 including a remote procedure call mechanism which forms a unique connection between a network element and a disk element through either the first or second switching element of the switch fabric at a certain priority through which requests and responses between the disk element and network element flow.

13. A system as described in claim 12 wherein the requests include NFS (network file system) requests.

14. A system as described in claim 13 wherein the requests include CIFS requests.

15. A system as described in claim 14 wherein the translator obtains the file IDs from path names contained within CIFS requests.

16. A method for responding to file system requests comprising the steps of:

receiving file system requests having file IDs comprising V, a volume identifier specifying the file system being accessed, and R, an integer, specifying the file within the file system being accessed at network elements, each having a mapping function that for every value of V, specifies one or more elements from the set D that store the data specified by volume V, the receiving step includes the step of obtaining the file ID from path names included in the requests with a translator of the network element, the receiving step includes the step of receiving requests at a network port of the network element which can respond to any request, and all the network elements and disk elements together appear as a single system; and

routing the requests to a switching fabric connected between the network elements and disk elements having a first switching element and second switching element, each of which is connected to each network element through unique connections to the network elements based on the file system request'"'"'s ID according to the mapping function and through the respective connections to disk elements connected to each of the switching elements of the switching fabric with the switching fabric processing higher priority requests before lower priority requests, the routing step includes the step of maintaining all disk element locations at each file system location database of each disk element and each network element so each network element can translate each file system request ID into a corresponding disk element location, the routing step includes the step of collecting from and distributing to the disk elements and the network elements, which form a cluster, which file systems are stored in each disk element by a cluster coordinator, which is one of the disk elements of the cluster, at predetermined times.

17. A method as described in claim 16 wherein the routing step includes the step of redistributing requests from any disk elements which are not operating properly to disk elements which are operating properly by the network elements which receive the requests.

18. A method as described in claim 17 wherein after the routing step, there is the step of adding dynamically network elements and disk elements to the cluster so the cluster appears as one server and any host connected to any network port can access any file located on any disk element.

19. A method as described in claim 18 wherein before the receiving step, there is the step of advertising by each network element each virtual interface it supports.