Virtualization of file input/output operations

• US 8,918,427 B1
• Filed: 12/29/2006
• Issued: 12/23/2014
• Est. Priority Date: 12/29/2006
• Status: Active Grant

• Current Assignee: Veritas Technologies, LLC (Whitehouse Group Ltd.)
• Original Assignee: Symantec Operating Corporation (NortonLifeLock Inc.)
• Inventors: Searls, Kirk L., Dickinson, Derek
• Primary Examiner(s): Woo, Isaac M
• Application Number:
  US11/647,796
• Time in Patent Office: 2,916 Days
• Field of Search: 707/205, 707/1, 707/100, 707/200, 707/999.1, 717/100, 717/120, 717/106, 726/5, 718/104, 718/100, 711/154
• US Class Current: 707/791
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• 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 16/1756 based on delta files
• CPC Class Codes: G06F 16/188 Virtual file systems
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: G06F 9/54 Interprogram communication

Abstract

Various embodiments of a system and method for providing input/output virtualization for a file are disclosed. The system may include a filter program that intercepts a write request for a particular file and stores change information specifying the data and the write location indicated by the write request. However, the file itself is not modified. The filter program may also intercept a read request referencing the file and determine whether change information representing a write request to write data at the location specified by the read request has been previously stored. If so then the data specified by the change information is returned in response to the read request.

Claims

1. A method for providing input/output virtualization for a first file, the method comprising:

intercepting, by a first program executing in a computer system, a first plurality of write requests, wherein each write request comprises a request to modify contents of the first file by writing data at a respective offset within the first file; and

storing, by the first program, for each of the write requests, change information in the computer system in response to the write request, wherein the change information specifies the data requested to be written within the first file and the offset indicated by the write request, wherein storing the change information records the write request without modifying the first file, and wherein the change information is stored in a location separate from the first file;

wherein the change information includes one or more data blocks, wherein each data block of the one or more data blocks is of a predetermined size.

2. The method of claim 1,

wherein a second program performs the first plurality of write requests by calling an application programming interface (API) of file system software;

wherein the first program intercepting the first plurality of write requests comprises the first program intercepting the first plurality of write requests in response to the second program calling the API of the file system software.

3. The method of claim 1, further comprising:

the first program intercepting a first read request, wherein the first read request comprises a request to read data at a first offset in the first file;

the first program determining whether first change information representing a write request to write data at the first offset has been stored;

the first program returning the data specified by the first change information in response to the first read request if the first change information is found; and

the first program forwarding the first read request to file system software if the first change information is not found, wherein the file system software returns the data at the first offset in the first file in response to the first read request.

4. The method of claim 3,

wherein a second program performs the first read request by calling an application programming interface (API) of file system software;

wherein the first program intercepting the first read request comprises the first program intercepting the first read request in response to the second program calling the API of the file system software.

5. The method of claim 1,

wherein, for each of the write requests, said first program storing change information in response to the write request comprises the first program storing the change information in one or more of a second file and/or a database.

6. The method of claim 1, further comprising:

storing information indicating that the change information for the first plurality of write requests is associated with a first ID;

the first program intercepting a second plurality of write requests;

the first program storing change information in response to each write request in the second plurality of write requests; and

the first program storing information indicating that the change information for the second plurality of write requests is associated with a second ID;

wherein the first ID identifies a first version of the first file and the second ID identifies a second version of the first file.

7. The method of claim 6,

wherein the first plurality of write requests includes a first write request to write first data at a first offset in the first file, wherein the first program stores first change information specifying the first data and the first offset, wherein the first change information is associated with the first ID;

wherein the second plurality of write requests includes a second write request to write second data at the first offset in the first file, wherein the first program stores second change information specifying the second data and the first offset, wherein the second change information is associated with the second ID.

8. The method of claim 7, further comprising:

setting a version indicator to one of the first ID or the second ID;

the first program intercepting a read request, wherein the read request comprises a request to read data at the first offset in the first file;

the first program returning the first data specified by the first change information in response to the read request if the version indicator is set to the first ID;

the first program returning the second data specified by the second change information in response to the read request if the version indicator is set to the second ID.

9. The method of claim 1,

wherein the first program includes a minifilter driver;

wherein said intercepting the first plurality of write requests comprises the minifilter driver intercepting the first plurality of write requests.

10. The method of claim 1, wherein the request to modify the contents of the first file by writing data comprises writing a M bytes of data, and wherein the predetermined size comprises N bytes of data, wherein M and N are positive integers, and M is less than N, and further comprising reading, by the first program, an additional number of bytes of the first file, wherein the additional number of bytes is dependent upon the difference between N and M.

11. A non-transitory computer-readable storage medium comprising program instructions executable to:

intercept a first plurality of write requests, wherein each write request comprises a request to modify contents of a first file by writing data at a respective offset within the first file; and

for each of the write requests, store change information in response to the write request, wherein the change information specifies the data requested to be written within the first file and the offset indicated by the write request, wherein storing the change information records the write request without modifying the first file, and wherein the change information is stored in a location separate from the first file;

wherein the change information includes one or more data blocks, wherein each data block of the one or more data blocks is of a predetermined size.

12. The non-transitory computer-readable storage medium of claim 11,

wherein a program performs the first plurality of write requests by calling an application programming interface (API) of file system software;

wherein said intercepting the first plurality of write requests comprises intercepting the first plurality of write requests in response to the program calling the API of the file system software.

13. The non-transitory computer-readable storage medium of claim 11, wherein the program instructions are further executable to:

intercept a first read request, wherein the first read request comprises a request to read data at a first offset within the first file;

determine whether first change information representing a write request to write data at the first offset has been stored;

return the data specified by the first change information in response to the first read request if the first change information is found; and

forward the first read request to file system software if the first change information is not found, wherein the file system software returns the data at the first offset in the first file in response to the first read request.

14. The non-transitory computer-readable storage medium of claim 11, wherein the program instructions are further executable to:

store information indicating that the change information for the first plurality of write requests is associated with a first ID;

intercept a second plurality of write requests;

store change information in response to each write request in the second plurality of write requests; and

store information indicating that the change information for the second plurality of write requests is associated with a second ID;

wherein the first ID identifies a first version of the first file and the second ID identifies a second version of the first file.

15. The non-transitory computer-readable storage medium of claim 14,

wherein the first plurality of write requests includes a first write request to write first data at a first offset in the first file, wherein first change information specifying the first data and the first offset is stored, wherein the first change information is associated with the first ID;

wherein the second plurality of write requests includes a second write request to write second data at the first offset in the first file, wherein second change information specifying the second data and the first offset is stored, wherein the second change information is associated with the second ID.

16. The non-transitory computer-readable storage medium of claim 15, wherein the program instructions are further executable to:

set a version indicator to one of the first ID or the second ID;

intercept a read request, wherein the read request comprises a request to read data at the first offset in the first file;

return the first data specified by the first change information in response to the read request if the version indicator is set to the first ID;

return the second data specified by the second change information in response to the read request if the version indicator is set to the second ID.

17. The non-transitory computer-readable storage medium of claim 11, wherein the request to modify the contents of the first file by writing data comprises writing a M bytes of data, and wherein the predetermined size comprises N bytes of data, wherein M and N are positive integers, and M is less than N, and wherein the program instructions are further executable to read an additional number of bytes of the first file, wherein the additional number of bytes is dependent upon the difference between N and M.

18. A system comprising:

a processor; and

a memory medium storing program instructions;

wherein the processor is operable to execute the program instructions to;

intercept a first plurality of write requests, wherein each write request comprises a request to modify contents of a first file by writing data at a respective offset within the first file; and

for each of the write requests, store change information in response to the write request, wherein the change information specifies the data requested to be written within the first file and the offset indicated by the write request, wherein storing the change information records the write request without modifying the first file, and wherein the change information is stored in a location separate from the first file;

wherein the change information includes one or more data blocks, wherein each data block of the one or more data blocks is of a predetermined size.

19. The system of claim 18,

wherein a program performs the first plurality of write requests by calling an application programming interface (API) of file system software;

wherein said intercepting the first plurality of write requests comprises intercepting the first plurality of write requests in response to the program calling the API of the file system software.

20. The system of claim 18, wherein the processor is further operable to execute the program instructions to:

intercept a first read request, wherein the first read request comprises a request to read data at a first offset in the first file;

determine whether first change information representing a write request to write data at the first offset has been stored;

return the data specified by the first change information in response to the first read request if the first change information is found; and

forward the first read request to file system software if the first change information is not found, wherein the file system software returns the data at the first offset in the first file in response to the first read request.

21. The system of claim 18, wherein the request to modify the contents of the first file by writing data comprises writing a M bytes of data, and wherein the predetermined size comprises N bytes of data, wherein M and N are positive integers, and M is less than N, and wherein the processor is further operable to execute the program instructions to read an additional number of bytes of the first file, wherein the additional number of bytes is dependent upon the difference between N and M.