Storage area network file system

• US 8,219,639 B2
• Filed: 05/28/2009
• Issued: 07/10/2012
• Est. Priority Date: 12/22/2000
• Status: Expired due to Term

• Current Assignee: Steven R. Soltis
• Original Assignee: Steven R. Soltis
• Inventors: Soltis, Steven R.
• Primary Examiner(s): Patel, Chirag R
• Application Number:
  US12/455,116
• Publication Number:
  US 20090240784A1
• Time in Patent Office: 1,139 Days
• Field of Search: 709217-219, 707821-822, 707/999.001
• US Class Current: 709/217
• CPC Class Codes: G06F 3/0605 by facilitating the interaction with a user or administrator
• CPC Class Codes: G06F 3/0635 by changing the path, e.g. traffic rerouting, path reconfiguration
• CPC Class Codes: G06F 3/0643 Management of files
• CPC Class Codes: G06F 3/0659 Command handling arrangements, e.g. command buffers, queues, command scheduling
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: Y10S 707/99931 Database or file accessing

Abstract

A shared storage distributed file system is presented that provides clients with access to a storage area network (SAN) attached storage device. The access is provided either via block-level requests over the SAN or via file-level requests made to a server over a local area network (LAN). File requests are categorized between SAN requests and LAN requests. This categorization can be based on dividing the requests between write and read requests, or between requests that alter data stored on the storage device and requests that do not alter data on the storage device. In other embodiments, the categorization can be made on the size of the file or the data involved in the file request. In one embodiment, the client is able to access and interpret metadata stored on the storage device.

Claims

1. A computer related article of manufacture, comprising:

a non-transitory computer readable medium having computer program code embodied therein, said computer program code adapted to be executed to implement a file system method for handling file requests by a file system, the implemented file system method comprising;

i) receiving the file requests on a client computer,

ii) categorizing each file request into either file-level requests or a block-level requests, wherein all write requests are categorized as file-level requests,

iii) submitting file-level requests to a server, and

iv) submitting block-level requests from the client computer to the storage device.

2. The article of manufacture of claim 1, wherein the storage device is block addressable and wherein the block-level requests address blocks on the block addressable storage device.

3. The article of manufacture of claim 1, wherein the storage device is object addressable and wherein the block-level requests address objects on the object addressable storage device.

4. The article of manufacture of claim 1, wherein the categorization is also determined in part by the data size of the file request or by the size of a file involved in the file request.

5. The article of manufacture of claim 1, wherein all file requests that modify data residing on the storage device are categorized as file-level requests, and at least some of the file requests that do not modify data residing on the storage device are categorized as block-level requests.

6. The article of manufacture of claim 5, wherein file requests that do not modify data residing on the storage devices are categorized as block-level requests when the implemented method determines that the file requests can be fulfilled through block-level requests to the storage device, and are categorized as file-level requests when the file requests cannot be fulfilled through block-level requests to the storage device.

7. The article of manufacture of claim 6, wherein the determination as to whether file requests can be fulfilled through block-level requests further comprises:

(1) determining a file involved in the file requests;

(2) retrieving a first modification time for the file at the client computer from the storage device;

(3) retrieving a second modification time for the file from the server; and

(4) comparing the two modification times.

8. The article of manufacture of claim 1, wherein the file system method further comprises analyzing metadata at the client computer.

9. The article of manufacture of claim 8, wherein the client computer interprets metadata received directly from the storage device.

10. The article of manufacture of claim 8, wherein the metadata is used in the categorization of file requests into file-level requests and block-level requests.

11. The article of manufacture of claim 8, wherein the metadata interpreted by the client computer is an inode.

12. The article of manufacture of claim 8, wherein the metadata interpreted by the client computer is a volume-level allocation table.

13. The article of manufacture of claim 1, wherein the storage device and the server together comprise a SAN appliance.

14. The article of manufacture of claim 1, wherein the server is comprised of multiple physical computers operating as a single logical server cluster.

15. The article of manufacture of claim 1, wherein the storage device is a logical collection of several physical devices.

16. A file system implemented as operating instructions stored on a non-transitory computer readable medium for a client computer communicating with a SAN-attached storage device over a SAN and communicating with a server computer over a LAN, the file system comprising:

a file system layer stored on the non-transitory computer readable medium that categorizes file requests that are received at the client computer into either SAN file requests to be sent to the SAN-attached storage device or LAN file requests to be sent to the server, wherein the categorization is determined in part by determining whether the file requests alter the SAN-attached storage device, wherein the file system layer categorizes a particular file request by;

a) determining a file involved in the particular file request;

b) retrieving a first modification time for the file at the client computer from the SAN-attached storage device;

c) retrieving a second modification time for the file from the server; and

d) comparing the two modification times.

17. A file system implemented as operating instructions stored on a non-transitory computer readable medium for a client computer communicating with a storage device over a SAN and communicating with a server computer over a LAN, the file system comprising:

a file system layer stored on the non-transitory computer readable medium that categorizes a plurality of file requests that are received at the client computer as either SAN file requests to be sent to the storage device or LAN file requests to be sent to the server, wherein the categorization is determined in part by at least one of;

a) examining the data size of the file request, and

b) examining the size of a file referenced in the file request.

18. The file system of claim 17, wherein the file request is received from an application running on the client computer.

19. The file system of claim 17, wherein the file request is received from a third computer communicating with the client computer.

20. The file system of claim 17, wherein the LAN communicates file-level requests and wherein the SAN communicates block-level requests, wherein the LAN and SAN are separate physical networks.

21. The file system of claim 17, wherein the LAN communicates file-level requests and wherein the SAN communicates block-level requests, wherein the LAN and SAN operate over the same physical network.

22. The file system of claim 17, wherein all file requests with a file size above a certain size are SAN file requests and all file requests with a file size below that certain size are LAN file requests.

23. The file system of claim 17, wherein all file requests having a data size above a certain size are SAN file requests and all file requests having a data size below that certain size are LAN file requests.

24. The file system of claim 17, wherein all write file requests are LAN file requests and wherein at least some read file requests are SAN file requests.

25. The file system of claim 24, wherein all read file requests having a data size above a certain size are SAN file requests and all read file requests having a data size below that certain size are LAN file requests.

26. A file system implemented as operating instructions stored on a non-transitory computer readable medium for a client computer communicating with a SAN-attached storage device over a SAN using block-level requests, the client computer also communicating with a server computer using file-level requests, the file system comprising:

a) a first file system component stored on a first non-transitory computer readable medium that categorizes file requests that are received at the client computer into either block-level requests to be sent to the SAN-attached storage device or file-level requests to be sent to the server; and

b) a second file system component stored on the first non-transitory computer readable medium or on a second non-transitory computer readable medium that services the block-level requests by

i) retrieving metadata relating to the file request directly from the SAN-attached storage device,

ii) interpreting at the client computer the metadata retrieved from the SAN-attached storage device, and

iii) initiating real-data transfer between the client computer and the SAN-attached storage device.

27. The file system of claim 26, wherein the first and second file system components are implemented as two different file system layers.

28. The file system of claim 26, wherein the first and second file system components are implemented in a single file system layer.

29. The file system of claim 26, wherein the metadata concerns a particular file referenced by the file request.

30. The file system of claim 29, wherein the metadata is an inode.

31. The file system of claim 26, wherein the metadata concerns a particular volume on the SAN-attached storage device.

32. The file system of claim 31, wherein the metadata is an allocation table.

33. A method for handling file requests within a file system of a computer comprising:

a) receiving read and write file requests made to the computer file system,

b) categorizing each file request in the computer file system into either a file-level request or a block-level request, the categorization being determined in part by at least one of;

i) examining the data size of the file request, and

ii) examining the size of a file referenced in the file request,

c) submitting file-level requests to a server for the server to submit the request to a storage device, and

d) submitting block-level requests directly to the storage device.

34. The method of claim 33, wherein all file requests with a file size above a certain size are block-level requests and all file requests with a file size below that certain size are file-level requests.

35. The method of claim 33, wherein all file requests having a data size above a certain size are block-level requests and all file requests having a data size below a certain size are file-level requests.

36. The method of claim 33, wherein all write file requests are file-level requests and wherein at least some read file requests are block-level requests.

37. The method of claim 33, wherein the storage device and the server together comprise a SAN appliance.

38. The method of claim 33, wherein the server is comprised of multiple physical computers operating as a single logical server cluster.

39. A method for maintaining data stored on a storage device that is accessed by a client computer over a storage area network, the method comprising:

a) receiving data requests concerning data stored on the storage device,

b) categorizing each request into either a SAN request or a server request, wherein all write requests are categorized as server requests,

c) submitting server requests from the client computer to a server for the server to submit the request to the storage device; and

d) submitting SAN requests from the client computer to the storage device over the storage area network.

40. The method of claim 39, wherein the categorization is also determined in part by the request size involved in the data request.

41. The method of claim 39, wherein all requests that modify data residing on the storage device are categorized as server requests, and at least some of the requests that do not modify data residing on the storage device are categorized as SAN requests.

42. The method of claim 39, wherein the requests are received from a third computer communicating with the client computer.

43. The method of claim 39, wherein the storage device is a logical collection of several physical devices.

44. A method for maintaining data on a data storage device comprising:

a) storing metadata and real-data on the data storage device;

b) serving metadata stored on the data storage device to a client computer for interpretation by the client computer;

c) serving metadata stored on the data storage device to a server for interpretation by the server computer;

d) serving real-data stored on the data storage device to the client computer; and

e) receiving real-data from the server computer that originated at the client computer.

45. The method of claim 44, further comprising

f) receiving real-data from the client computer.

46. The method of claim 45, further comprising

g) serving real-data stored on the data storage device to the server for retransmittal to the client computer.

47. The method of claim 45, further comprising:

g) receiving metadata generated by the server from the server; and

h) receiving metadata generated by the client computer from the client computer.

48. The method of claim 44, wherein the metadata is at least one of an inode and a volume-level allocation table.

49. The method of claim 44, wherein the data storage device and the server together comprise a SAN appliance.

50. A method for handling file requests within a file system of a computer comprising:

a) receiving a file request concerning a file stored on a SAN-attached storage device;

b) categorizing the file request into either a block-level request or a file-level request, the categorization being determined in part by comparing a file attribute concerning the file received from the SAN-attached storage device via a storage area network with a second file attribute concerning the file received from a server via a local area network,

c) submitting file-level requests to the server over the local area network for the server to submit the request to the SAN-attached storage device, and

d) submitting block-level requests from the client computer to the SAN-attached storage device over the storage area network.

51. An article of manufacture in the form of a non-transitory computer readable medium having a computer program embodied therein adapted to be executed to implement a file system method comprising:

a) receiving a file request concerning a file stored on a SAN-attached storage device;

b) categorizing the file request into either a SAN file request or a LAN file request, the categorization being determined in part by comparing a file attribute concerning the file received from the SAN-attached storage device via a storage area network with a second file attribute concerning the file received from a server via a local area network,

c) submitting LAN file requests to the server over the local area network for the server to submit the request to the SAN-attached storage device, and

d) submitting SAN file requests from the client computer to the SAN-attached storage device over the storage area network.

52. A computer related article of manufacture, comprising:

a non-transitory computer readable medium having computer program code embodied therein, said computer program code adapted to be executed to implement a file system method for handling file requests by a file system, the implemented file system method comprising;

i) receiving the file requests on a client computer;

ii) categorizing each file request into either file-level requests or a block-level requests, the categorization being determined in part by whether the file request modifies data residing on a storage device;

iii) submitting file-level requests to a server; and

iv) submitting block-level requests from the client computer to the storage device;

wherein the file system method handles file write requests relating to a file by;

(1) requesting the server lock the file,

(2) allocating data blocks to the file, wherein the allocating of data blocks to the file is handled by requesting the server to lock an allocation table, reading the allocation table at the client computer directly by making block-level requests to the storage device, revising the allocation table at the client computer, writing the revised allocation table from the client computer directly to the storage device, and requesting the server to unlock the allocation table,

(3) submitting block-level write requests to the storage device for storage, and

(4) requesting the server to unlock the file.

53. The article of manufacture of claim 52, wherein the allocating of data blocks to the file is handled by the server after receiving a request from the client computer.