Lookup optimization during online file system migration

• US 8,943,019 B1
• Filed: 04/13/2011
• Issued: 01/27/2015
• Est. Priority Date: 04/13/2011
• Status: Expired due to Fees

• Current Assignee: Veritas Technologies, LLC (Whitehouse Group Ltd.)
• Original Assignee: Symantec Corporation (NortonLifeLock Inc.)
• Inventors: Patwardhan, Kedar, Naik, Neha, Jain, Sanjay Kumar, Patil, Sushil Sarjerao
• Primary Examiner(s): Le, Miranda
• Application Number:
  US13/085,671
• Time in Patent Office: 1,385 Days
• Field of Search: 707/610, 707/821, 707/999.204
• US Class Current: 707/610
• CPC Class Codes: G06F 16/119 Details of migration of file systems migration mechanisms in storage systems G06F3/0647

Abstract

A system and method for migrating file systems is provided. A file system migration operation copies a plurality of files from a first file system to a second file system. A request to access one of the files being migrated during the file system migration operation results in the creation of a pseudo vnode for the file being requested in the second file system. The pseudo vnode is created prior to creating a vnode for the file in the second file system. In addition, the pseudo vnode is associated with a vnode of the file at the first file system. Information identifying the pseudo vnode is then returned to the application.

Claims

1. A method comprising:

receiving a request to access a file from an application, wherein

the request is received during a file system migration operation,

the file system migration operation copies a plurality of files from a first file system to a second file system, and

the plurality of files comprises the file;

determining whether the file has been copied from the first file system to the second file system at the time the request is received;

if the file has not been copied from the first file system to the second file system at the time the request is received,

creating a pseudo vnode for the file, prior to creation of a vnode for the file, in the second file system, wherein

the pseudo vnode includes information that enables the application to obtain the file from the first file system, and

the pseudo vnode is created instead of copying the file from the first file system to the second file system at the time the request is received,

creating an association between the pseudo vnode in the second file system and a vnode of the file at the first file system, wherein

the association establishes a connection path between the pseudo vnode in the second file system and the vnode of the file at the first file system, and

returning information identifying the pseudo vnode to the application, wherein

the pseudo vnode and the association allow the application to locate and access the file in the first file system without having to create the file in the second file system, and

the information identifying the pseudo vnode allows the application to perform an operation on the file at the first file system;

if the file has been copied from the first file system to the second file system at the time the request is received, returning information identifying the file at the first and second file systems to the application, wherein

the information identifying the file at the first and second file systems allows the application to perform the operation on the file at the first and second file systems; and

copying an existing file from the first file system to the second file system when the existing file is closed at the first file system.

2. The method of claim 1, wherein

the association is a link.

3. The method of claim 1, wherein

the information identifying the pseudo vnode identifies the association between the pseudo vnode and the vnode of the file at the first file system.

4. The method of claim 1, further comprising:

performing the operation on the file at the first file system, wherein

the operation is performed using the association.

5. The method of claim 1, further comprising:

removing the association between the pseudo vnode and the vnode of the file at the first file system, wherein

the association is removed after the file system migration operation is complete.

6. The method of claim 1, further comprising:

creating the file at the second file system; and

associating the pseudo vnode with the vnode for the file at the second file system.

7. The method of claim 1, further comprising:

performing the operation on the file at the first file system, if the file has not been copied from the first file system to the second file system at the time the request is received; and

performing the operation on the file at the first and second file systems, if the file has been copied from the first file system to the second file system at the time the request is received.

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

receive a request to access a file from an application, wherein

the request is received during a file system migration operation,

the file system migration operation copies a plurality of files from a first file system to a second file system, and

the plurality of files comprises the file;

determine whether the file has been copied from the first file system to the second file system at the time the request is received;

if the file has not been copied from the first file system to the second file system at the time the request is received,

create a pseudo vnode for the file, prior to creation of a vnode for the file in the second file system, wherein

the pseudo vnode includes information that enables the application to obtain the file from the first file system, and

the pseudo vnode is created instead of copying the file from the first file system to the second file system at the time the request is received,

create an association between the pseudo vnode in the second file system and a vnode of the file at the first file system, wherein

the association establishes a connection path between the pseudo vnode in the second file system and the vnode of the file at the first file system, and

return information identifying the pseudo vnode to the application, wherein

the pseudo vnode and the association allow the application to locate and access the file in the first file system without having to create the file in the second file system, and

the information identifying the pseudo vnode allows the application to perform an operation on the file at the first file system;

if the file has been copied from the first file system to the second file system at the time the request is received, return information identifying the file at the first and second file systems to the application, wherein

the information identifying the file at the first and second file systems allows the application to perform the operation on the file at the first and second file systems; and

copy an existing file from the first file system to the second file system when the existing file is closed at the first file system.

9. The non-transitory computer readable storage medium of claim 8, wherein

the association is a link.

10. The non-transitory computer readable storage medium of claim 8, wherein

the information identifying the pseudo vnode identifies the association between the pseudo vnode and the vnode of the file at the first file system.

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

perform the operation on the file in the first file system, wherein

the operation is performed using the association.

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

remove the association between the pseudo vnode and the vnode of the file at the first file system, wherein

the association is removed after the file system migration operation is complete.

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

create the file at the second file system; and

associate the pseudo vnode with the vnode for the file at the second file system.

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

perform the operation on the file at the first file system, if the file has not been copied from the first file system to the second file system at the time the request is received; and

perform the operation on the file at the first and second file systems, if the file has been copied from the first file system to the second file system at the time the request is received.

15. A system comprising:

one or more processors; and

memory coupled to the one or more processors, wherein the memory stores program instructions executable by the one or more processors to;

receive a request to access a file from an application, wherein

the request is received during a file system migration operation,

the file system migration operation copies a plurality of files from a first file system to a second file system, and

the plurality of files comprises the file,

determine whether the file has been copied from the first file system to the second file system at the time the request is received,

if the file has not been copied from the first file system to the second file system at the time the request is received,

create a pseudo vnode for the file, prior to creation of a vnode for the file, in the second file system, wherein

the pseudo vnode includes information that enables the application to obtain the file from the first file system, and

the pseudo vnode is created instead of copying the file from the first file system to the second file system at the time the request is received,

create an association between the pseudo vnode in the second file system and a vnode of the file at the first file system, wherein

the association establishes a connection path between the pseudo vnode in the second file system and the vnode of the file at the first file system, and

return information identifying the pseudo vnode to the application, wherein

the pseudo vnode and the association allow the application to locate and access the file in the first file system without having to create the file in the second file system, and

the information identifying the pseudo vnode allows the application to perform an operation on the file at the first file system,

if the file has been copied from the first file system to the second file system at the time the request is received, return information identifying the file at the first and second file systems to the application, wherein

the information identifying the file at the first and second file systems allows the application to perform the operation on the file at the first and second file systems, and

copy an existing file from the first file system to the second file system when the existing file is closed at the first file system.

16. The system of claim 15, wherein

the information identifying the pseudo vnode identifies the association between the pseudo vnode and the vnode of the file at the first file system.

17. The system of claim 15, wherein the program instructions are further executable to:

perform the operation on the file in the first file system, wherein

the operation is performed using the association.

18. The system of claim 15, wherein the program instructions are further executable to:

create the file at the second file system, and

associate the pseudo vnode with the vnode for the file at the second file system.

19. The system of claim 15, wherein the program instructions are further executable to:

perform the operation on the file at the first file system, if the file has not been copied from the first file system to the second file system at the time the request is received, and

perform the operation on the file at the first and second file systems, if the file has been copied from the first file system to the second file system at the time the request is received.