Use of application-level context information to detect corrupted data in a storage system

• US 20060075281A1
• Filed: 09/27/2004
• Published: 04/06/2006
• Est. Priority Date: 09/27/2004
• Status: Abandoned Application

• Current Assignee: NetApp, Inc.
• Original Assignee: NetApp, Inc.
• Inventors: Kimmel, Jeffrey S., Sundaram, Rajesh, Hamilton, Eric C., Sankar, Sunitha S., Muppalaneni, Nitin, Eng, Emily W.
• Application Number:
  US10/951,644
• Publication Number:
  US 20060075281A1
• Time in Patent Office: Days
• US Class Current: 714/5
• CPC Class Codes: G06F 11/073 in a memory management context, e.g. virtual memory or cache management memory management G06F12/00; testing of static memory units G11C29/00
• CPC Class Codes: G06F 11/1076 Parity data used in redundant arrays of independent storages, e.g. in RAID systems
• CPC Class Codes: G06F 2211/1007 Addressing errors, i.e. silent errors in RAID, e.g. sector slipping and addressing errors
• CPC Class Codes: G06F 2211/104 Metadata, i.e. metadata associated with RAID systems with parity

Abstract

A storage system, such as a file server, receives a request to perform a write operation that affects a data block. In response, the storage system writes to a storage device the data block together with context information which uniquely identifies the write operation with respect to the data block. When the data block is subsequently read from the storage device together with the context information, the context information that was read with the data block is used to determine whether a previous write of the data block was lost.

Claims

1. A method comprising:

in response to a request to perform a write operation that affects a data block, writing to a storage device the data block together with context information which uniquely identifies the write operation with respect to the data block;

reading the data block and the context information together from the storage device, and

using the context information that was read with the data block to determine whether the data block is valid.

2. A method as recited in claim 1, wherein said reading the data block and said using the context information are in response to a read request relating to the data block.

3. A method as recited in claim 1, wherein using the context information that was read with the data block to determine whether the data block is valid comprises:

comparing the context information that was read with the data block to corresponding context information from an application; and

determining that a previous write of the data block was lost if the context information that was read with the data block does not match the corresponding context information from the application.

4. A method as recited in claim 3, wherein the application is a file system.

5. A method as recited in claim 4, wherein said determining whether the data block is valid is performed by the file system.

6. A method as recited in claim 3, wherein said determining whether the data block is valid is performed by a RAID layer.

7. A method as recited in claim 1, wherein the method is performed in a storage system that includes a file system, and wherein the context information is information generated by the file system.

8. A method as recited in claim 1, wherein the context information includes a file block number identifying a block within a file, to which the data block corresponds.

9. A method as recited in claim 8, wherein the context information includes an identifier corresponding to a root of a hierarchical structure in which the data block is referenced.

10. A method as recited in claim 9, wherein the identifier represents an inode of the data block.

11. A method as recited in claim 8, wherein the context information includes a generation indication indicating a generation of the data block.

12. A method as recited in claim 1, further comprising, prior to writing the data block and the context information together to the storage device:

appending metadata about the data block to the data block, the metadata including the context information and a checksum for use in detecting an error in the data block.

13. A method as recited in claim 1, further comprising, prior to writing the data block and the context information together to the storage device:

incorporating the context information into the data block.

14. A method comprising:

storing in a storage device a data block with file system context information generated by a file system about the data block;

retrieving the data block and the file system context information from the storage device; and

using the retrieved file system context information to determine whether a previous write of the data block was lost.

15. A method as recited in claim 14, wherein said storing is in response to a request to perform a write operation that affects the data block;

and

wherein the file system context information uniquely identifies the write operation with respect to the data block.

16. A method as recited in claim 14, wherein using the retrieved file system context information to determine whether a previous write of the data block was lost comprises:

comparing the retrieved file system context information to corresponding file system context information from the file system; and

determining that a previous write of the data block was lost if the retrieved file system context information does not match the corresponding file system context information from the file system.

17. A method as recited in claim 14, wherein said using the retrieved file system context information to determine whether a previous write of the data block was lost is performed by a file system in a storage server.

18. A method as recited in claim 14, wherein said using the retrieved file system context information to determine whether a previous write of the data block was lost is performed by a RAID layer in a storage server.

19. A method as recited in claim 14, wherein the file system context information includes a file block number identifying a block within a file, to which the data block corresponds.

20. A method as recited in claim 19, wherein the file system context information includes an identifier corresponding to a root of a hierarchical structure in which the data block is referenced.

21. A method as recited in claim 20, wherein the identifier represents an inode of the data block.

22. A method as recited in claim 19, wherein the file system context information includes a generation indication indicating a generation of the data block.

23. A method as recited in claim 14, wherein the file system context information is incorporated into the data block when stored in the storage device.

24. A method as recited in claim 14, wherein the file system context information is appended to the data block when stored in the storage device.

25. A method as recited in claim 14, further comprising, prior to said storing the file system context information and the data block:

appending metadata about the data block to the data block, the metadata including the file system context information and a checksum for use in detecting an error in the data block.

26. A method comprising:

receiving a request to perform a write operation that affects a data block;

in response to the write request,

computing a checksum for use in detecting an error in the data block,

appending metadata about the data block to the data block, the metadata including the checksum,

including in the metadata file system context information generated by a file system, and

writing the data block with the metadata appended thereto to a storage device in a single write operation; and

using the file system context information in the metadata appended to the data block to determine whether a previous write of the data block was lost.

27. A method as recited in claim 26, wherein the context information uniquely identifies the write operation with respect to the data block.

28. A method as recited in claim 26, wherein using the system context information in the metadata appended to the data block to determine whether the data block is corrupted comprises:

reading the data block and the metadata appended thereto from storage device;

comparing the file system context information in the metadata with corresponding file system context information about the data block from the file system, after the block is read from the storage device; and

determining that a previous write of the data block was lost if the file system context information obtained from the metadata does not match the corresponding file system context information about the data block from the file system.

29. A method as recited in claim 26, wherein said using the file system context information in the metadata appended to the data block to determine whether a previous write of the data block was lost is in response to a read request received by the storage system.

30. A method as recited in claim 26, wherein the file system context information includes a file block number identifying a block within a file, to which the data block corresponds.

31. A method as recited in claim 30, wherein the file system context information includes an identifier corresponding to a root of a hierarchical structure in which the data block is referenced.

32. A method as recited in claim 31, wherein the identifier represents an inode of the data block.

33. A method as recited in claim 30, wherein the file system context information includes a generation indication indicating a generation of the data block.

34. A method as recited in claim 26, further comprising:

in a RAID layer, receiving the metadata about the data block from the file system prior to appending the metadata to the data block, wherein said appending metadata to the data block is performed by the RAID layer; and

in the RAID layer, retrieving the file system context information from the metadata appended to the block after the block is read from the storage device.

35. A method as recited in claim 34, wherein said comparing the file system context information is performed by the RAID layer.

36. A method as recited in claim 34, further comprising:

passing the retrieved file system context information from the RAID layer to the file system, wherein said comparing the file system context information and said determining that the data block is corrupted are performed by the file system.

37. A method of operating a storage system, the method comprising:

using a file system in the storage system to store data in an array of storage devices using a hierarchical data storage structure;

receiving a write request relating to a data block to be written to the array of storage devices;

computing a checksum for use in detecting an error in the data block;

appending metadata about the data block to the data block, the metadata including the checksum;

including in the metadata file system context information generated by the file system, the file system context information relating to the data block;

writing the data block with the metadata appended thereto to the array of storage devices in a single write operation;

receiving a read request relating to the data block;

reading the data block and the metadata appended thereto from the array of storage devices, in response to the read request;

comparing the file system context information in the metadata with corresponding file system context information about the data block from the file system, after the block is read from the array of storage devices; and

determining that a previous write of the data block was lost if the file system context information obtained from the metadata does not match the corresponding file system context information about the data block from the file system.

38. A storage system comprising:

a file system to maintain a hierarchical structure of data stored in an array of storage devices and to service read and write requests from one or more clients relating to data stored in the array of storage devices, the file system further to generate, in response to a request to perform a write operation, file system context information that uniquely identifies the write operation relative to a data block;

a storage access module to control access to data stored in the array of storage devices in response to the file system, the storage access module further to receive the file system context information from the file system and to write the data block and the file system context information together to the array;

the storage access module further to respond to a read request relating to the data block by reading the data block and the file system context information together from the storage device; and

an error detection module to determine whether the data block is valid using the file system context information that was read with the data block.

39. A storage system as recited in claim 38, wherein the storage access module implements a RAID protocol.

40. A storage system as recited in claim 38, wherein the storage access module appends the file system context information to the data block.

41. A storage system as recited in claim 38, wherein the storage access module incorporates the file system context information into the data block.

42. A storage system as recited in claim 38, wherein the error detection module determines whether the data block is valid by:

comparing the file system context information that was read with the data block to corresponding file system context information from the file system; and

determining that the data block is valid if the file system context information that was read with the data block does not match the corresponding file system context information from the file system.

43. A storage system as recited in claim 38, wherein the error detection module is part of the file system.

44. A storage system as recited in claim 38, wherein the error detection module is part of the storage access module.

45. A storage system as recited in claim 38, wherein the file system context information includes a file block number identifying a block within a file, to which the data block corresponds.

46. A storage system as recited in claim 45, wherein the file system context information includes an identifier corresponding to a root of a hierarchical structure in which the data block is referenced.

47. A storage system as recited in claim 46, wherein the identifier represents an inode of the data block.

48. A storage system as recited in claim 46, wherein the file system context information includes a generation indication indicating a generation of the data block.

49. A storage server comprising:

a network interface through which to communicate with one or more clients over a network;

a storage interface through which to communicate with an array of storage devices;

a processor to implement a file system for data stored in the array of storage devices; and

a memory storing instructions which, when executed by the processor, cause the storage server to perform a set of operations, including

responding to a received request to perform a write operation that affects a data block, by

obtaining context information generated by the file system about the data block, and

writing the data block and the context information together to a storage device in the array; and

responding to a read request relating to the data block, by

reading the data block and the context information from the storage device, and

using the context information that was read with the data block to determine whether a previous write of the data block was lost.

50. A storage server as recited in claim 49, wherein the context information uniquely identifies the write operation with respect to the data block.

51. A storage server as recited in claim 49, further comprising, prior to writing the data block and the context information together to the storage device:

appending metadata about the data block to the data block, the metadata including the context information and a checksum for use in detecting an error in the data block.

52. A storage server as recited in claim 49, further comprising, prior to writing the data block and the context information together to the storage device:

incorporating the context information into the data block.

53. A storage server as recited in claim 49, wherein using the context information that was read with the data block to determine whether the data block is corrupted comprises:

comparing the context information that was read with the data block to corresponding context information from the file system; and

determining that a previous write of the data block was lost if the context information that was read with the data block does not match the corresponding context information from the file system.

54. A storage server as recited in claim 49, wherein said using the context information that was read with the data block to determine whether the data block is corrupted is performed by the file system.

55. A storage server as recited in claim 49, wherein said using the context information that was read with the data block to determine whether a previous write of the data block was lost is performed by a RAID layer.

56. A storage server as recited in claim 49, wherein the context information includes a file block number identifying a block within a file, to which the data block corresponds.

57. A storage server as recited in claim 56, wherein the context information includes an identifier corresponding to a root of a hierarchical structure in which the data block is referenced.

58. A storage server as recited in claim 57, wherein the identifier represents an inode of the data block.

59. A storage server as recited in claim 56, wherein the context information includes a generation indication indicating a generation of the data block.

60. A storage system comprising:

means for storing file system context information about a data block with the data block in a storage device;

means for retrieving the data block with the file system context information from the storage device; and

means for using the file system context information stored with the data block to determine whether the data block is valid.