TOKEN BASED FILE OPERATIONS

• US 20130041985A1
• Filed: 08/10/2011
• Published: 02/14/2013
• Est. Priority Date: 08/10/2011
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Christiansen, Neal R., Green, Dustin L., Pinkerton, James T., Nagar, Rajeev, Matthew, Bryan Stephen, Aithal, Jaivir K.
• Application Number:
  US13/207,014
• Publication Number:
  US 20130041985A1
• Time in Patent Office: Days
• US Class Current: 709/219
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]

Abstract

Described are embodiments which allow token-based file operations. The client may request a special offload file operation that is formatted according to a file access protocol. The file operation may be an offload read operation or an offload write operation. In an offload read operation, the client requests that data be logically read from a stored file, or a portion thereof. In response, the file server provides a response that includes a token that represents the logically read data. In some embodiments, the file server may return a response with a token that represents less than all of the requested data if for some reason it cannot provide a token that represents all of the data. The token can then be used by the client in a subsequent offload write operation. In embodiments, the tokens represent immutable data that can be safely and securely used across servers and clients.

Claims

1. A computer implemented method of providing token based file operations, the method comprising:

receiving at a file server a first request to connect to the file server to access information in a file system;

sending a first response from the file server, the response establishing a session with a client for allowing access to the information in the file system;

receiving at the file server a second request to open a file in the file system to access file information from the file;

in response to receiving the second request, the file server sending a second response to the client granting access to the file;

receiving at the file server a third request for an offload read of first data from a portion of the file, the third request being formatted according to a file access protocol; and

in response to receiving the third request, the file server sending a third response with a token representing the first data, wherein the first data is logically read from the portion of the file, and wherein the third response is formatted according to the file access protocol.

2. The method of claim 1, wherein the file access protocol is a version of the Server Message Block (SMB) protocol.

3. The method of claim 1, wherein the token is generated by the file server.

4. The method of claim 1, wherein the token is generated by an underlying file storage system.

5. The method of claim 1, wherein the third response includes a response indicating that the token represents less than all of the first data requested in the third request.

6. The method of claim 1, wherein the third request indicates first data to be read from the file and second data to be read from the file, and the third response includes the token representing the first data and a second token representing the second data.

7. The method of claim 1, wherein the third request indicates a first portion of a first file and a second portion of a second file and the third response includes the token representing first data logically read from the first portion of the first file and a second token representing second data logically read from the second portion of the second file.

8. The method of claim 1, further comprising:

receiving at the file server a fourth request for an offload write of a requested portion of the first data to a second file, the fourth request including the token and being formatted according to the file access protocol; and

in response to receiving the fourth request, the file server;

writing the requested portion of the first data to the second file; and

sending a fourth response indicating the requested portion of the first data was written to the second file, the fourth response being formatted according to the file access protocol.

9. The method of claim 1, further comprising:

receiving at the file server a fourth request for an offload write of a requested portion of the first data to a second file, the fourth request including the token and being formatted according to the file access protocol; and

in response to receiving the fourth request, the file server;

writing a first portion of the requested portion of the first data to the second file, wherein the first portion of the requested portion is less than all of the requested portion of the first data; and

sending a fourth response indicating the first portion of the requested portion of the first data was written to the second file, the fourth response being formatted according to the file access protocol.

10. The method of claim 9, wherein the third request is received from the client and the fourth request is received from a second client different from the client.

11. The method of claim 2, wherein the third request is a

12. The method of claim 9, wherein the file access protocol is a version of the Server Message Block (SMB) protocol, and wherein the fourth request is a FSCTL_OFFLOAD_WRITE request.

13. The method of claim 1, wherein the token is formatted according to a Small Computer System Interface (SCSI) standard.

14. A computer readable storage medium comprising computer executable instructions that when executed by a processor perform a method of requesting token based file operations, the method comprising:

sending by a client a first request to connect to a file server to access information in a file system;

receiving a first response, the response establishing a session with the client for allowing access to the file information;

sending a second request to open a file in the file system;

receiving a second response granting access to the file;

sending a third request for an offload write of a first portion of data represented by a token to a file, the third request being formatted according to a version of the Server Message Block (SMB) protocol and including the token representing the data; and

receiving a response.

15. The computer readable storage medium of claim 14, wherein the token was generated by the server.

16. The computer readable storage medium of claim 14, wherein the response indicates that a second portion of the data was successfully written to the file, and wherein the second portion represents less than all of the data in the first portion.

17. The computer readable storage medium of claim 14, further comprising:

sending a fourth request for an offload read of second data from a portion of a second file, the fourth request being formatted according to the version of the SMB protocol; and

receiving a fourth response with a token representing the second data, the fourth response being formatted according to the version of the SMB protocol.

18. A system for allowing token based file operations, the system comprising:

at least one server comprising;

at least one processor configured to execute computer executable instructions;

at least one computer readable storage media storing the computer executable instructions that when executed by the at least one processor provide;

a file server configured to;

receive a request for an offload read of data from a portion of a file, the request being formatted according to a version of the Server Message Block (SMB) protocol; and

in response to receiving the request, the file server sending a response with a token representing the data, the response being formatted according to the version of the SMB protocol.

19. The system of claim 18, wherein the system further comprises:

at least one client, comprising;

at least one processor configured to execute computer executable instructions;

at least one computer readable storage media storing the computer executable instructions that when executed by the at least one processor;

sends the request for the offload read of data from the portion of the file; and

receives the response with the token representing the data.

20. The system of claim 19, wherein the computer readable storage media stores computer executable instructions that when executed by the at least one processor:

sends an offload write request with the token to write a portion of the data to a second file.