Systems and methods for data migration in a clustered file system

• US 10,387,069 B2
• Filed: 01/22/2016
• Issued: 08/20/2019
• Est. Priority Date: 03/31/2009
• Status: Active Grant

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: CommVault Systems Incorporated
• Inventors: Erofeev, Andrei
• Primary Examiner(s): Featherstone, Mark D
• Assistant Examiner(s): Gmahl, Navneet
• Application Number:
  US15/004,634
• Publication Number:
  US 20160139854A1
• Time in Patent Office: 1,306 Days
• CPC Class Codes: G06F 12/0864 using pseudo-associative means, e.g. set-associative or hashing
• CPC Class Codes: G06F 12/0891 using clearing, invalidating or resetting means
• CPC Class Codes: G06F 16/1744 using compression, e.g. sparse files
• 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: G06F 2212/60 Details of cache memory
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/0643 Management of files
• CPC Class Codes: G06F 3/0647 Migration mechanisms
• CPC Class Codes: G06F 3/0683 Plurality of storage devices

Abstract

Systems and methods for providing more efficient handling of I/O requests for clustered file system data subject to data migration or the like. For instance, exemplary systems can more quickly determine if certain files on primary storage represent actual file data or stub data for recalling file data from secondary storage. Certain embodiments utilize a driver cache on each cluster node to maintain a record of recently accessed files that represent regular files (as opposed to stubs). A dual-locking process, using both strict locking and relaxed locking, maintains consistency between driver caches on different nodes and the data of the underlying clustered file system, while providing improved access to the data by the different nodes. Moreover, a signaling process can be used, such as with zero-length files, for alerting drivers on different nodes that data migration is to be performed and/or that the driver caches should be flushed.

Claims

1. A computer-implemented method for coordinating access to data in a storage management system, the method comprising:

requesting with one or more computers, a read-only lock on a signal file, wherein the locking status of the signal file indicates whether a migration operation is about to occur;

in response to the request for the read-only lock on the signal file being denied;

clearing with the one or more computers, an associated cache storing information regarding whether a given file stored on a primary storage device are associated with a stub file type, and

operating in a first locking mode associated with requests to access the given file, said operating in the first locking mode comprising refraining from using the associated cache to determine whether the given file is associated with the stub file type; and

in response to the request for the read-only lock on the signal file being granted;

unlocking the signal file and re-requesting the read-only lock on the signal file with the one or more computers after a predetermined period of time, and

operating in a second locking mode associated with the requests to access the given file, the second locking mode less strict than the first locking mode, said operating in the second locking mode comprising;

determining whether the associated cache includes information regarding the given file,

in response to determining that the associated cache does not include information regarding the given file, analyzing a size or content of one or more inodes associated with the given file to determine whether the given file is associated with the stub file type, and

in response to determining that the associated cache includes information regarding the given file, determining whether the given file is associated with the stub file type based on the information stored in the associated cache.

2. The method of claim 1, wherein the requesting is performed by file system drivers of the one or more computers.

3. The method of claim 1, additionally comprising, when said request for the read-only lock is denied, releasing a second read-only lock on a token file.

4. The method of claim 3, additionally comprising performing migration of the given file only after no second read-only locks by the one or more computers remain on the token file.

5. The method of claim 3, additionally comprising obtaining with a migration service an exclusive lock on both the signal and token files prior to performing the migration.

6. The method of claim 3, wherein the signal file and the token file each comprises a zero-length file.

7. The method of claim 1, additionally comprising populating the associated cache with at least one or more inodes associated with the given file.

8. The method of claim 1, wherein the one or more computers is an independent node of a clustered file system.

9. The method of claim 1, wherein the predetermined period of time is between approximately two seconds and approximately ten seconds.

10. A system that coordinates access to data, the system comprising:

one or more computers that request a read-only lock on a signal file;

in response to the request for the read-only lock on the signal file being denied;

the one or more computers are configured to clear an associated cache storing information regarding whether a given file stored on a primary storage device are associated with a stub file type, and

the one or more computers are further configured to operate in a first locking mode associated with requests to access the given file, wherein in the first locking mode, the one or more computers are further configured to refrain from using the associated cache to determine whether the given file is associated with the stub file type; and

in response to the request for the read-only lock on the signal file being granted;

the one or more computers are further configured to unlock the signal file and re-request the read-only lock on the signal file with the one or more computers after a predetermined period of time, and

the one or more computers are further configured to operate in a second locking mode associated with the requests to access the given file, the second locking mode less strict than the first locking mode, wherein in the second locking mode, the one or more computers are further configured to;

determine whether the associated cache includes information regarding the given file,

in response to determining that the associated cache does not include information regarding the given file, analyzing a size or content of one or more inodes associated with the given file to determine whether the given file is associated with the stub file type, and

in response to determining that the associated cache includes information regarding the given file, determine whether the given file is associated with the stub file type based on the information stored in the associated cache.

11. The system of claim 10, wherein the request is performed by file system drivers of the one or more computers.

12. The system of claim 10, additionally comprising, when said request for the read-only lock is denied, releasing a second read-only lock on a token file.

13. The system of claim 12, wherein the one or more computers are further configured to perform migration of the given file only after no second read-only locks remain on the token file.

14. The system of claim 12, additionally comprising a migration service that obtains an exclusive lock on both the signal and token files prior to performing the migration.

15. The system of claim 12, wherein of the signal file and the token file each comprises a zero-length file.

16. The system of claim 10, additionally wherein the one or more computers are further configured to populate the associated cache with at least one or more inodes associated with the given file.

17. The system of claim 10, wherein the one or more computers comprise an independent node of a clustered file system.

18. The system of claim 10, wherein the predetermined period of time is between approximately two seconds and approximately ten seconds.