Error checking file system metadata while the file system remains available

• US 20060282471A1
• Filed: 06/13/2005
• Published: 12/14/2006
• Est. Priority Date: 06/13/2005
• Status: Abandoned Application

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Akers, David G., Mark, Timothy W.
• Application Number:
  US11/151,011
• Publication Number:
  US 20060282471A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/08 Error detection or correction by redundancy in data representation, e.g. by using checking codes
• CPC Class Codes: G06F 16/128 Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion use of snapshots for error detection or correction G06F11/14, G06F11/16

Abstract

File system metadata associated with a file system is stored. A snapshot of the file system metadata is created, and a change of the file system is allowed while the snapshot is being created. An error check is run with respect to the snapshot of the file system metadata to check for an error in the snapshot of the file system metadata while the file system remains available. Access of one or more files associated with the file system is enabled while the error check is being run with respect to the snapshot of the file system metadata.

Claims

1. A method of software execution comprising:

storing file system metadata associated with a file system;

creating a snapshot of the file system metadata;

performing at least a first type of write to change user data while the snapshot is being created;

running an error check with respect to the snapshot of the file system metadata to check for an error in the snapshot of the file system metadata while the file system remains available; and

allowing access of user data associated with the file system while the error check is being run with respect to the snapshot of the file system metadata.

2. The method of claim 1, wherein performing the first type of write comprises performing a non-extending write.

3. The method of claim 1, wherein performing the first type of write comprises performing a write that changes the user data without changing file system metadata synchronously with the change of the user data.

4. The method of claim 1, wherein creating the snapshot occurs even though dirty data resides in a cache that has not been flushed to persistent storage.

5. The method of claim 1, wherein running the error check comprises performing a consistency check of the snapshot of file system metadata.

6. The method of claim 5, wherein performing the consistency check comprises cross-checking different pieces of the snapshot of the file system metadata to determine consistency between the different pieces.

7. The method of claim 5, wherein performing the consistency check comprises at least one of (1) checking a storage map of files to determine that the storage map accurately reflects actual files stored on a storage medium, (2) checking a value of at least one information field in the snapshot of the metadata to determine whether the value is within an expected range, and (3) verifying that the file system metadata accurately indicates a file is located in a particular directory.

8. The method of claim 1, wherein creating the snapshot comprises copying the file system metadata into the snapshot without copying the user data into the snapshot.

9. The method of claim 1, further comprising the file system continuing access of the stored file system metadata while the error checking is being run with respect to the snapshot of the file system metadata.

10. The method of claim 9, further comprising:

storing user data associated with the file system metadata in the one or more files; and

enabling access of the user data based on file system access of the stored file system metadata while the error check is being performed with respect to the snapshot of the file system metadata.

11. The method of claim 1, wherein creating the snapshot comprises creating the snapshot of an entirety of the stored file system metadata.

12. A system comprising:

software;

a storage subsystem to store user data and file system metadata associated with the user data;

file system logic to access the user data based on the file system metadata;

snapshot logic to create a snapshot of the file system metadata stored in the storage subsystem, the snapshot containing a copy of the file system metadata but not a copy of the user data; and

a checker utility to perform error checking of the snapshot of the file system metadata while the file system logic remains available to the software for accessing user data.

13. The system of claim 12, wherein the software comprises application software,

wherein the application software is able to access the user data through the file system logic while the checker utility performs the error checking with respect to the snapshot of the file system metadata.

14. The system of claim 13, wherein the file system logic is adapted to access the stored file system metadata to enable access by the application software of the user data while the checker utility performs error checking with respect to the snapshot of the file system metadata.

15. The system of claim 12, wherein the checker utility is adapted to perform the error checking by performing consistency checking of the snapshot of the file system metadata.

16. The system of claim 15, wherein the consistency checking comprises cross-checking different pieces of the snapshot of the file system metadata to determine consistency between the different pieces.

17. The system of claim 15, wherein the consistency checking comprises at least one of (1) checking a storage map of files to determine that the storage map accurately reflects actual files stored on a storage medium, (2) checking a value of at least one information field in the snapshot of the file system metadata to determine whether the value is within an expected range, and (3) verifying that the file system metadata accurately indicates a file is located in a particular directory.

18. The system of claim 12, further comprising a snapshot application created through a programming interface by a user, the snapshot application to send a command to the snapshot logic to create the snapshot of the file system metadata.

19. The system of claim 18, the snapshot application to detect an event to send the command to the snapshot logic.

20. The system of claim 19, wherein the event comprises a time event.

21. The system of claim 12, wherein a change of a file system is allowed while the snapshot is being created, the file system including the file system logic, the file system metadata, and the user data.

22. The system of claim 21, wherein the change of the file system is caused by a non-extending write.

23. The system of claim 21, wherein the change of the file system is caused by a write that changes user data without changing file system metadata synchronously with the change of the user data.

24. An article comprising at least one storage medium containing instructions that when executed cause a system to:

store file system metadata associated with user data;

create a snapshot of the file system metadata;

perform a change of a file system during creation of the snapshot; and

run an error check with respect to the snapshot of the file system metadata to check for an error in the snapshot of the file system metadata while the stored file system metadata is accessible by software to access user data associated with the stored file system metadata.

25. The article of claim 24, wherein performing the change of the file system comprises performing a non-extending write.

26. The article of claim 24, wherein the instructions when executed cause the system to enable the file system to access the user data based on the stored file system metadata while the error check is being run with respect to the snapshot of the file system metadata.

27. The article of claim 24, wherein the snapshot of the file system metadata represents a copy of the stored file system metadata at a given point in time.

28. The article of claim 24, wherein running the error check with respect to the snapshot of the file system metadata comprises running a consistency check with respect to the snapshot of the file system metadata.

29. The article of claim 28, wherein running the consistency check comprises cross-checking different pieces of the file system metadata to determine consistency between the different pieces.

30. The article of claim 29, wherein running the consistency check comprises at least one of (1) checking a storage map of files to determine that the storage map accurately reflects actual files stored on a storage medium, (2) checking a value of at least one information field in the snapshot of the file system metadata to determine whether the value is within an expected range, and (3) verifying that the file system metadata accurately indicates a file is located in a particular directory.

31. The article of claim 24, wherein creating the snapshot comprises copying the file system metadata into the snapshot without copying the user data into the snapshot.

32. A computer comprising:

software;

a file system including snapshot logic;

a storage subsystem to store user data and file system metadata, the file system to organize and access the user data based on the file system metadata,

the snapshot logic to create a snapshot of an entirety of the file system metadata stored in the storage subsystem, the snapshot not including the user data, wherein a non-extending write is allowed to change the file system during creation of the snapshot; and

a checker utility to perform a consistency check of the snapshot,

the file system to continue to access the user data using the file system metadata while the checker utility performs the consistency check.