File server having a file system cache and protocol for truly safe asynchronous writes

• US 5,893,140 A
• Filed: 11/13/1996
• Issued: 04/06/1999
• Est. Priority Date: 08/14/1996
• Status: Expired due to Term

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Tzelnic, Percy, Gupta, Uday, Porat, Betti, Vahalia, Uresh K
• Primary Examiner(s): Swann, Tod R.
• Assistant Examiner(s): Langjahr, David
• Application Number:
  US08/747,631
• Time in Patent Office: 874 Days
• Field of Search: 395/842, 395/182.13, 395/200.33, 711/161, 711/118, 207/205, 439/73, 706/908
• US Class Current: 711/118
• CPC Class Codes: G06F 11/1435 using file system or storage system metadata
• CPC Class Codes: G06F 12/0804 with main memory updating G06F12/0806 takes precedence
• CPC Class Codes: G06F 12/0813 with a network or matrix configuration
• CPC Class Codes: G06F 12/0866 for peripheral storage systems, e.g. disk cache
• CPC Class Codes: G06F 16/1774 Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: Y10S 706/908 Electronic or computer, internal or network, circuit

Abstract

A conventional network file server has a file system that permits file attributes and file data to be written in any order. The conventional network file server may also support an asynchronous write protocol, in which file attributes and file data need not be written to disk storage until a client sends a commit request. This asynchronous write protocol has a data security problem if the attributes are written before the data and the server crashes before completing the writing of the data to disk storage. This security problem is solved by adding a file system cache and following a protocol that writes the attributes to storage after writing the data to storage. For example, the attributes and data are stored in the file system cache and are not written down to storage until receipt of a commit request. When the commit request is received, the data is sent first from the file system cache to storage. Then the attributes are sent from the file system cache to storage. Then the file server acknowledges completion of the commit operation. In a preferred embodiment, storage is provided by an integrated cached disk array (ICDA) having a buffer cache and an array of disk drives, and the file system cache is distributed in a plurality of data mover computers interfaced to the ICDA. The addition of the file system cache to solve the security problem also reduces the burden on the buffer cache in the ICDA.

Claims

1. A method of operating a file server having a cache memory and storage, said method comprising the steps of:

(a) the file server receiving a write request from a client, and in response to the write request, writing new file attributes to the cache memory and thereafter writing new file data to the cache memory, and acknowledging to the client completion of a write operation before writing the new file attributes and the new file data to the storage, the new file attributes including pointers to locations in the storage where the new file data is written; and

thereafter

(b) the file server receiving a commit request from the client, and in response to the commit request, acknowledging to the client completion of a commit operation after the new file attributes and the new file data are written to the storage;

wherein the file server writes the new file attributes to the storage after the file server writes the new file data to the storage.

2. The method as claimed in claim 1, wherein the new file attributes and the new file data are not written to the storage until the file server receives the commit request from the client.

3. The method as claimed in claim 1, wherein the file server writes the new file attributes from the cache memory to the storage, and the file server writes the new file data from the cache memory to the storage.

4. The method as claimed in claim 1, wherein the storage includes a battery-backed semiconductor random access memory and disk storage, and the file server acknowledges to the client completion of the commit operation after the new file attributes and the new file data are written to the battery-backed semiconductor random access memory, and the file server writes the new file attributes and the new file data from the battery-backed semiconductor random access memory to the disk storage after acknowledging to the client completion of the commit operation.

5. A method of operating a file server having a volatile semiconductor cache memory and nonvolatile storage, said method comprising the steps of:

(a) the file server receiving a write request from a client, and in response to the write request, writing new file attributes to the volatile semiconductor cache memory and thereafter writing new file data to the volatile semiconductor cache memory, and acknowledging to the client completion of a write operation before writing the new file attributes and the new file data to the nonvolatile storage, the new file attributes including pointers to locations in the nonvolatile storage where the new file data is written; and

thereafter

(b) the file server receiving a commit request from the client, and in response to the commit request, acknowledging to the client completion of a commit operation after the new file attributes and the new file data are written to the nonvolatile storage;

wherein the file server writes the new file attributes to the nonvolatile storage after the file server writes the new file data to the nonvolatile storage.

6. The method as claimed in claim 5, wherein the new file attributes and the new file data are not written to the nonvolatile storage until the file server receives the commit request from the client, the file server writes the new file attributes from the volatile semiconductor cache memory to the nonvolatile storage, and the file server writes the new file data from the volatile semiconductor cache memory to the nonvolatile storage.

7. The method as claimed in claim 5, wherein the nonvolatile storage includes a battery-backed semiconductor random access memory and disk storage, and the file server acknowledges to the client completion of the commit operation after the new file attributes and the new file data are written to the battery-backed semiconductor random access memory, and the file server writes the new file attributes and the new file data from the battery-backed semiconductor random access memory to the disk storage after acknowledging to the client completion of the commit operation.

8. A method of operating a file server having a cache memory and nonvolatile storage, the method comprising the steps of:

(a) the file server receiving a write request from a client, and in response to the write request, writing new file attributes to the cache memory and thereafter writing new file data to the cache memory, and acknowledging to the client completion of a write operation before writing the new file attributes and the new file data to the nonvolatile storage, the new file attributes including pointers to locations in the nonvolatile storage where the new file data is written; and

thereafter

(b) the file server receiving a commit request from the client, and in response to the commit request, writing the new file data from the cache memory to the nonvolatile storage and thereafter writing the new file attributes from the cache memory to the nonvolatile storage, and acknowledging to the client completion of a commit operation after the new file attributes and the new file data are written to the nonvolatile storage;

wherein the file server does not write the new file attributes and the new file data to the nonvolatile storage until after the file server receives the commit request from the client.

9. The method as claimed in claim 8, wherein the nonvolatile storage includes a battery-backed semiconductor random access memory and disk storage, and the file server acknowledges to the client completion of the commit operation after the new file attributes and the new file data are written to the battery-backed semiconductor random access memory, and the file server writes the new file attributes and new file data from the battery-backed semiconductor random access memory to the disk storage after acknowledging to the client completion of the commit operation.

10. A file server comprising, in combination:

a cache memory;

storage;

means responsive to a write request from a client for writing new file attributes to the cache memory and thereafter writing new file data to the cache memory, and acknowledging to the client completion of a write operation before writing the new file attributes and the new file data to the storage, the new file attributes including pointers to locations in the storage where the new file data is written;

means for writing the new file data to the storage and thereafter writing the new file attributes to the storage; and

means responsive to a commit request from the client for acknowledging to the client completion of a commit operation after the new file attributes and new file data are written to the storage.

11. The file server as claimed in claim 10, wherein the storage includes a battery-backed semiconductor random access memory and disk storage, and wherein the means responsive to a commit request from the client includes means for acknowledging to the client completion of the commit operation after the new file attributes and the new file data are written to the battery-backed semiconductor random access memory and before the new file attributes and the new file data are written to the disk storage.

12. A file server comprising, in combination:

a cache memory;

storage;

means responsive to a write request from a client for writing new file attributes to the cache memory and thereafter writing new file data to the cache memory, and acknowledging to the client completion of a write operation before writing the new file attributes and new file data to the storage, the new file attributes including pointers to locations in the storage where the new file data is written; and

means responsive to a commit request from the client for writing the new file data from the cache memory to the storage, and thereafter writing the new file attributes from the cache memory to the storage, and thereafter acknowledging to the client completion of a commit operation.

13. The file server as claimed in claim 12, wherein the storage includes a battery-backed semiconductor random access memory and disk storage, and wherein the means responsive to a commit request from the client includes means for acknowledging to the client completion of the commit operation after the new file attributes and the new file data are written to the battery-backed semiconductor random access memory and before the new file attributes and the new file data are written to the disk storage.

14. A file server comprising, in combination:

a file system layer for mapping file names to data storage locations in response to a write request from a client;

a file system cache connected to the file system layer for storing new file attributes and new file data in response to the write request from the client; and

nonvolatile storage connected to the file system layer for storing the new file attributes and the new file data in response to a commit request from the client;

wherein the file system layer is programmed for responding to the write request from the client by writing the new file attributes to the file system cache and thereafter writing the new file data to the file system cache, and acknowledging to the client completion of a write operation before writing the new file attributes and the new file data to the nonvolatile storage, the new file attributes including pointers to locations in the nonvolatile storage where the new file data is written; and

wherein the file system layer is programmed for responding to the commit request from the client by writing the new file data from the file system cache to the nonvolatile storage and thereafter writing the new file attributes from the file system cache to the nonvolatile storage, and thereafter acknowledging to the client completion of the commit operation.

15. The file server as claimed in claim 14, wherein the file system layer is programmed so as not to write any of the new file attributes and any of the new file data from the file system cache to the nonvolatile storage until receipt of the commit request from the client.

16. The file server as claimed in claim 14, wherein the file system layer is programmed with a Network File System (NFS) version providing an asynchronous write file access protocol.

17. The file server as claimed in claim 14, wherein the nonvolatile storage includes a battery-backed semiconductor random access memory and disk storage connected to the battery-backed semiconductor memory for writing data from the battery-backed semiconductor memory to the disk storage, and the file system layer is programmed to acknowledge to the client completion of the commit operation after the new file attributes and the new file data are written to the battery-backed semiconductor random access memory and before the new file attributes and the new file data are written to the disk storage.

18. A file server comprising, in combination:

a file system layer for mapping file names to data storage locations in response to a write request from a client;

a file system cache connected to the file system layer for storing new file attributes and new file data in response to the write request from the client; and

a buffer cache including random access memory connected to the file system layer for storing the new file attributes and the new file data in response to a commit request from the client;

disk storage; and

a storage layer connected to the buffer cache and disk storage for performing management of the buffer cache including setting write pending flags and later writing data from the buffer cache to the disk storage as directed by the write pending flags;

wherein the file system layer is programmed for responding to the write request from the client by writing the new file attributes to the file system cache and thereafter writing the new file data to the file system cache, and acknowledging to the client completion of a write operation before writing the new file attributes and the new file data to the storage layer, the new file attributes including pointers to locations in the disk storage where the new file data is written; and

wherein the file system layer is programmed for responding to the commit request from the client by writing the new file data from the file system cache to the storage layer, and after receiving an acknowledgement from the storage layer that the new file data has been written in the buffer cache, writing the new file attributes from the file system cache to the storage layer, and after receiving an acknowledgement from the storage layer that the new file attributes have been written in the buffer cache, acknowledging to the client completion of the commit operation.

19. The file server as claimed in claim 18, wherein the file system layer is programmed so as not to write any of the new file attributes and any of the new file data from the file system cache to the storage layer until receipt of the commit request from the client.

20. The file server as claimed in claim 18, wherein the file system layer is programmed with a Network File System (NFS) version providing an asynchronous write file access protocol.

21. The file server as claimed in claim 18, wherein the storage layer, the buffer cache, and the disk storage are backed by a battery having a capacity sufficient to power the storage layer, the buffer cache, and the disk storage from an occurrence of a power supply failure until all write pending data in the buffer cache is written into the disk storage.

22. The file server as claimed in claim 18, wherein the storage layer, the buffer cache, and the disk storage comprise an integrated cached disk array.

23. A file server comprising, in combination:

a computer including a file system layer for mapping file names to data storage locations in response to a write request from a client, and a file system cache connected to the file system layer for storing new file attributes and new file data in response to the write request from the client; and

an integrated cached disk array including a random access memory buffer cache and an array of disk drives, the integrated cached disk array being connected to the computer for storing the new file attributes and the new file data;

wherein the file system layer is programmed for responding to the write request from the client by writing the new file attributes to the file system cache, thereafter writing the new file data to the file system cache, and thereafter acknowledging to the client completion of a write operation before writing the new file attributes and the new file data to the integrated cached disk array, and not writing any of the new file attributes and any of the new file data to the integrated cached disk array until receipt of the commit request, the new file attributes including pointers to disk storage locations where the new file data is written in the integrated cached disk array; and

wherein the file system layer is programmed for responding to the commit request from the client by writing the new file data from the file system cache to the integrated cached disk array, and after receiving an acknowledgement from the integrated cached disk array that the new file data has been written in the buffer cache, writing the new file attributes from the file system cache to the integrated cached disk array, and after receiving an acknowledgement from the integrated cached disk array that the new file attributes have been written in the buffer cache, acknowledging to the client completion of the commit operation.

24. The file server as claimed in claim 23, wherein the file system layer is programmed with a Network File System (NFS) version providing an asynchronous write file access protocol.

25. The file server as claimed in claim 23, which includes a plurality of computers;

each computer including a file system layer for mapping file names to data storage locations in response to a write request to said each computer from a respective client, and a file system cache connected to the file system layer for storing new file attributes and new file data in response to the write request to said each computer from the respective client; and

wherein said each computer is connected to the integrated cached disk array for storing the new file attributes and the new file data from said each computer.