File storage system, cache appliance, and method

• US 9,323,681 B2
• Filed: 09/18/2008
• Issued: 04/26/2016
• Est. Priority Date: 09/18/2008
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Avere Systems, Inc. (Microsoft Corporation)
• Inventors: Apostolides, Vasilis J., Bertschi, Jason, Boyles, John R., Hosteny, Joseph Nevi IV, Kazar, Michael L.
• Primary Examiner(s): Beausoliel, Jr., Robert
• Assistant Examiner(s): BROMELL, ALEXANDRIA Y
• Application Number:
  US12/283,961
• Publication Number:
  US 20100094806A1
• Time in Patent Office: 2,777 Days
• Field of Search: 707/769, 707/716, 713/185, 709/248
• US Class Current: 1/1
• CPC Class Codes: G06F 12/0804 with main memory updating G06F12/0806 takes precedence
• CPC Class Codes: G06F 12/0815 Cache consistency protocols
• CPC Class Codes: G06F 12/0866 for peripheral storage systems, e.g. disk cache
• CPC Class Codes: G06F 16/172 Caching, prefetching or hoarding of files
• CPC Class Codes: G06F 16/1767 Concurrency control, e.g. optimistic or pessimistic approaches
• CPC Class Codes: G06F 16/183 Provision of network file services by network file servers, e.g. by using NFS, CIFS network file access protocols H04L67/1097
• CPC Class Codes: G06F 2212/264 Remote server
• CPC Class Codes: G06F 2212/284 being distributed
• CPC Class Codes: G06F 2212/314 In storage network, e.g. network attached cache
• CPC Class Codes: G06F 2212/463 File

Abstract

A file storage system for storing data of a file received from a client includes a back-end file server in which the data is stored. The system includes a cache appliance in communication with the file server, such that the appliance stores portions of the data or attributes of the file, and uses the stored data or attributes to process file system requests received from the client, and which reads and writes data and attributes to the back-end file server independently. A system for responding to a file system protocol request in regard to a back-end server includes a token server. The system includes a plurality of cache appliances in communication with the token server, each of which receives tokens from the token server to synchronize access to data and attributes caches of the cache appliances, and reading and writing data and attributes to the back-end servers when tokens are revoked, the cache appliance having persistent storage in which data are stored, and the token server having persistent storage in which tokens are stored. A storage system includes a plurality of backend servers. The system includes a token server which grants permission to read and write file attributes and data system, and includes a plurality of cache appliances in communication with at least one of the backend servers and the token server for processing an incoming NFS request to the one backend server. Each cache appliance comprises an NFS server which converts incoming NFS requests into cache manager operations; a token client module in communication with the token server having a cache of tokens obtained from the token server; a cache manager that caches data and attributes and uses tokens from the token client module to ensure that the cached data or attributes are the most recent data or attributes, and an NFS client which sends outgoing NFS requests to the back-end file server. Methods for storing data of a file received from a client.

Claims

1. A system for responding to a file system protocol request in regard to a back-end server comprising:

a primary token server;

a plurality of cache appliances in communication with the token server, each of which receives tokens from the token server to synchronize access to data and attributes caches of the cache appliances by revoking incompatible tokens when granting new tokens, and reading and writing data and attributes to the back-end server when tokens are revoked, the cache appliance having persistent storage in which data and attributes are stored, and the token server having persistent storage in which tokens are stored and where the cache appliance maintains its own copy of modified data and attributes, and stores them to the back-end file server upon revocation of a write token, wherein the token server produces a write data token to write data to the back-end server by the cache appliance, and ensures that no two write data tokens are granted over a single byte of any same file, wherein the token server produces write attribute tokens for files stored in the back-end server and ensures that no two write attribute tokens are granted for the same file, and wherein the token server revokes an already granted write data or write attribute token by recalling the granted write data or write attribute token if a new write data or write attribute token is requested from the token server and is incompatible with the already granted write attribute or write data token and when a write data or write attribute token is revoked, the cache appliance writes the modified version of the file'"'"'s data or attributes to the back-end file server; and

a hot spare token server to which the write data tokens and write attribute tokens are mirrored, the hot spare token server replaces the primary token server if the primary token server fails and continues operation with a reconstructed token database, if the hot spare token server replaces the primary token server, the hot spare server becomes the primary token server and each write data token and write attribute token that is mirrored in the hot spare token server is revoked in a same way as when a corresponding write data token or read data token is revoked in the primary token server, the token server produces hold modified tokens for the cache appliance for the file'"'"'s attributes and data, and data and attributes associated with the hold modified tokens are retrieved directly from the cache appliance having the hold modified tokens, the hold modified tokens identify the cache appliance having the hold modified tokens.

2. A system as described in claim 1 including another cache appliance where modified data and modified attributes are mirrored and persistently stored.

3. A system as described in claim 1 wherein the token server produces read data tokens and read attribute tokens that have a per token expiration time which allows them to be unilaterally revoked by the token server after the expiration time has passed.

4. A system as described in claim 1 where the token server produces batch tokens to reduce communication with the token server for shared files.

5. A system as described in claim 1 wherein dual logs, or a circular log, is used to store tokens persistently at the token server.

6. A system as described in claim 1 wherein a token server is chosen by a function including a file handle as a parameter, which maps the file handle to a plurality of token servers, with a plurality of token servers in communication with the plurality of cache appliances.

7. A method for responding to a file system protocol request in regard to a back-end server comprising the steps of:

receiving tokens from a primary token server in communication with a plurality of cache appliances;

synchronizing access to data caches and attributes caches of the cache appliances with the tokens by revoking incompatible tokens when granting new tokens;

reading and writing file data and attributes in the caches of the cache appliances holding tokens;

writing data in the data caches and attributes in the attributes caches to a back-end server when the tokens are revoked, the cache appliance having persistent storage in which the data and attributes are stored, and the token server having persistent storage in which tokens are stored;

mirroring in a hot spare token server the write data tokens and write attribute tokens, the hot spare token server replaces the primary token server if the primary token server fails and continues operation with a reconstructed token database, if the hot spare token server replaces the primary token server, the hot spare server becomes the primary token server and each write data token and write attribute token that is mirrored in the hot spare token server is revoked in a same way as when a corresponding write data token or read data token is revoked in the primary token server;

producing write attribute tokens by the token server for files stored in the back-end server, the token server ensuring that no two write attribute tokens are granted for the same file;

the token server revoking an already granted write data or write attribute token by recalling the granted write data or write attribute token if a new write data or write attribute token is requested from the token server and is incompatible with the already granted write attribute or write data token; and

producing with the token server ownership tokens for the cache appliance for the file'"'"'s attributes and data to allow the cache appliance to read data from another cache appliance.

8. A method as described in claim 7 including the step of the production of a write data token by the token server for files stored in the back-end server, the token server ensuring that no two write data tokens are granted over a single byte of any same file.

9. A method as described in claim 7 including the step of persistently storing in another cache appliance modified data and modified attributes synchronously with respect to the incoming data update request.

10. A method as described in claim 7 including the step of producing with the token server read data tokens and read attribute tokens that have a per token expiration time which allows them to be unilaterally revoked by the token server after the expiration time has passed.

11. A method as described in claim 7 including the step of retrieving directly from the cache appliance data and attributes of files for which the cache appliance holds an ownership token.

12. A method as described in claim 7 including the step of the token server producing a ghost token persisting for a time period during which the token server indicates a last time in which a write data or attribute token was held for the file.

13. A method as described in claim 7 including the step of the token server producing batch tokens to reduce communication with the token server for shared files.

14. A system for responding to a file system protocol request in regard to a back-end server comprising:

a primary token server;

a plurality of cache appliances in communication with the token server, each of which receives tokens from the token server to synchronize access to data and attributes caches of the cache appliances by revoking incompatible tokens when granting new tokens, and reading and writing data and attributes to the back-end server when tokens are revoked, the cache appliance having persistent storage in which data and attributes are stored, and the token server having persistent storage in which tokens are stored and where the cache appliance maintains its own copy of modified data and attributes, and stores them to the back-end file server upon revocation of a write token, wherein the token server produces a write data token to write data to the back-end server by the cache appliance, and ensures that no two write data tokens are granted over a single byte of any same file, wherein the token server produces write attribute tokens for tiles stored in the back-end server and ensures that no two write attribute tokens are granted for the same file, and wherein the token server revokes an already granted write data or write attribute token by recalling the granted write data or write attribute token if a new write data or write attribute token is requested from the token server and is incompatible with the already granted write attribute or write data token and when a write data or write attribute token is revoked, the cache appliance writes the modified version of the file'"'"'s data or attributes to the back-end file server; and

a hot spare token server to which the write data tokens and write attribute tokens are mirrored, the hot spare token server replaces the primary token server if the primary token server fails and continues operation with a reconstructed token database, if the hot spare token server replaces the primary token server, the hot spare server becomes the primary token server and each write data token and write attribute token that is mirrored in the hot spare token server is revoked in a same way as when a corresponding write data token or read data token is revoked in the primary token server, the token server produces a ghost token persisting for a limited time period after revocation of an original token upon granting of a new token conflicting with the ghost token, an indication is returned to the new token'"'"'s owner, indicating that the new token would have conflicted with the original token if the new token had been requested earlier, allowing the owner of the new token to act as if the new token had been obtained earlier than it was requested.

15. A method for responding to a file system protocol request in regard to a back-end server comprising the steps of:

receiving tokens from a primary token server in communication with a plurality of cache appliances;

synchronizing access to data caches and attributes caches of the cache appliances with the tokens by revoking incompatible tokens when granting new tokens;

reading and writing file data and attributes in the caches of the cache appliances holding tokens;

writing data in the data caches and attributes in the attributes caches to a back-end server when the tokens are revoked, the cache appliance having persistent storage in which the data and attributes are stored, and the token server having persistent storage in which tokens are stored;

mirroring in a hot spare token server the write data tokens and write attribute tokens, the hot spare token server replaces the primary token server if the primary token server fails and continues operation with a reconstructed token database, if the hot spare token server replaces the primary token server, the hot spare server becomes the primary token server and each write data token and write attribute token that is mirrored in the hot spare token server is revoked in a same way as when a corresponding write data token or read data token is revoked in the primary token server; and

choosing the token server by a function which includes a file handle as a parameter using hashing, which maps the file handle to a plurality of token servers.

16. A method for responding to a file system protocol request in regard to a back-end server comprising the steps of:

receiving tokens from a primary token server in communication with a plurality of cache appliances;

synchronizing access to data caches and attributes caches of the cache appliances with the tokens by revoking incompatible tokens when granting new tokens;

reading and writing file data and attributes in the caches of the cache appliances holding tokens;

writing data in the data caches and attributes in the attributes caches to a back-end server when the tokens are revoked, the cache appliance having persistent storage in which the data and attributes are stored, and the token server having persistent storage in which tokens are stored;

mirroring in a hot spare token server the write data tokens and write attribute tokens, the hot spare token server replaces the primary token server if the primary token server fails and continues operation with a reconstructed token database, if the hot spare token server replaces the primary token server, the hot spare server becomes the primary token server and each write data token and write attribute token that is mirrored in the hot spare token server is revoked in a same way as when a corresponding write data token or read data token is revoked in the primary token server; and

leasing the read data tokens and read attribute tokens and automatically revoking them when their lease expires, which prevents read access to the data and the attributes associated with the read data tokens and read attribute tokens.