Method and system for responding to file system requests

• US 7,917,693 B2
• Filed: 01/08/2008
• Issued: 03/29/2011
• Est. Priority Date: 12/07/2000
• Status: Active Grant

• 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/008,143
• Publication Number:
  US 20080133772A1
• Time in Patent Office: 1,176 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 including a plurality of network elements with at least a network element of the plurality of network elements receiving the requests. The system includes a plurality of switching elements in communication with the network elements which route the requests. The system includes a plurality of disk elements in which files are stored and which respond to the requests in communication with the switching elements, the network element insures each request from the network element is only executed once, the network element retransmits each request for which the network element does not receive an acknowledgment from the switching elements. A method for responding to file system requests.

Claims

1. A system for responding to file system requests comprising:

a plurality of network elements with at least a network element of the plurality of network elements receiving the requests;

a plurality of switching elements in communication with the network elements which route the requests; and

a plurality of disk elements in which files are stored and which respond to the requests in communication with the switching elements, the plurality of network elements insure each request from the network element is only executed once, the network element retransmits each request for which the network element does not receive an acknowledgment from the switching elements.

2. A system as described in claim 1 wherein the network elements authenticate the requests.

3. A system as described in claim 2 wherein the network element parses the request.

4. A system as described in claim 3 wherein the network element parses the request into a sequence of file-level file system requests.

5. A system as described in claim 4 wherein the network element translates each request into a back plane file system protocol.

6. A system as described in claim 5 wherein the network elements, switching elements and disk elements are disposed in a server.

7. A system as described in claim 6 wherein the network element determines which disk element stores the file associated with each file request.

8. A system as described in claim 7 wherein the network element sends each request to the disk element having the associated file.

9. A system as described in claim 8 wherein the disk elements include directories whose contents implement a data structure that maps a file name within a directory into a file ID.

10. A system as described in claim 9 including a file system location data base.

11. A system as described in claim 10 wherein the network element interprets requests in POP, SMTP or IMAP protocols in terms of SpinFS operations.

12. A system as described in claim 11 wherein the network element issues look up requests for associated files in the disk elements.

13. A system as described in claim 12 wherein the network element issues read requests for associated files in the disk elements.

14. A system as described in claim 13 wherein the network element issues write requests to write the data into associated files.

15. A system as described in claim 14 wherein the network element issues create file requests to create a file in the disk elements.

16. A system as described in claim 15 wherein the network element issues create directory requests for associated files in the disk elements.

17. A system as described in claim 16 wherein the network element issues a remove a file request for an associated file in the disk elements.

18. A system as described in claim 17 wherein the network element issues a rename a file request for an associated file in the disk elements.

19. A system as described in claim 18 wherein the network element issues a request to lock a file from reading or writing with respect to the file.

20. A system as described in claim 19 wherein 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.

21. A system as described in claim 20 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.

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

23. A system as described in claim 22 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.

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

receiving each request at a network element of a plurality of network elements;

routing each request with at least one switching element of a plurality of switching elements in communication with the network elements;

responding to each request with at least one disk element of a plurality of disk elements in which files are stored in communication with the switching elements, each request from the network element being executed only once; and

retransmitting by the network element each request for which the network element does not receive an acknowledgment from the switching elements.

25. A method as described in claim 24 including the step of authenticating each request with the network element.

26. A method as described in claim 25 including the step of parsing each request with the network element.

27. A method as described in claim 26 including the step of parsing each request into a sequence of file-level file method requests with the network element.

28. A method as described in claim 27 including the step of translating each request into a back plane file method protocol with the network element.

29. A method as described in claim 28 including the step of determining with the network element which disk element stores the file associated with each request.

30. A method as described in claim 29 including the step of sending each request with the network element to the disk element having the associated file.

31. A method as described in claim 30 wherein the disk elements include directories, and including the step of implementing a data structure that maps a file name within a directory into a file ID.

32. A method as described in claim 31 including the step of interpreting with the network element requests in POP, SMTP or IMAP protocols in terms of SpinFS operations.

33. A method as described in claim 32 including the step of issuing with the network element look up requests for associated files in the disk elements.

34. A method as described in claim 33 including the step of issuing with the network element read requests for associated files in the disk elements.

35. A method as described in claim 34 including the step of issuing with the network element write requests to write the data into associated files.

36. A method as described in claim 35 including the step of issuing with the network element create file requests to create a file in the disk elements.

37. A method as described in claim 36 including the step of issuing with the network element create directory requests for associated files in the disk elements.

38. A method as described in claim 37 including the step of issuing with the network element a remove a file request for an associated file in the disk elements.

39. A method as described in claim 38 including the step of issuing with the network element a rename a file request for an associated file in the disk elements.

40. A method as described in claim 39 including the step of issuing with the network element a request to lock a file from reading or writing with respect to the file.

41. A method as described in claim 40 including the step of forming a cluster with the disk elements, 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 methods are stored in each disk element of the cluster.

42. A method as described in claim 41 including the steps of determining with the cluster coordinator if each disk element is operating properly and redistributing requests for any disk element that is not operating properly;

and allocating virtual network interfaces to network elements and assigning responsibility for the virtual network interfaces to network elements for a failed network element.

43. A method as described in claim 42 including the step of advertising by each network element the virtual interfaces it supports to all disk elements.

44. A method as described in claim 43 wherein each request has an active disk element and a passive disk element associated with each request, and including the step of responding with the passive disk element to the request if the active disk element fails.