Method and apparatus for data version checking

• US 20040250028A1
• Filed: 06/09/2003
• Published: 12/09/2004
• Est. Priority Date: 06/09/2003
• Status: Abandoned Application

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Patterson, Brian, Lindemann, Aaron, Daniels, Rodger D.
• Application Number:
  US10/457,895
• Publication Number:
  US 20040250028A1
• Time in Patent Office: Days
• US Class Current: 711/156
• CPC Class Codes: G06F 11/0727 in a storage system, e.g. in a DASD or network based storage system drivers for digital recording or reproducing units G06F3/06; circuits for error detection or correction within digital recording or reproducing units G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097
• CPC Class Codes: G06F 11/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06
• 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 block of data is written to a location on a first storage system. Version checking data associated with the block of data and having a predetermined initial value is also written to the first storage system. The version checking data is then written to a second storage system. Upon subsequent writing of data to the same location on the first storage system, the version checking data on the first storage system is incremented and the incremented version checking data is stored on the second storage system. When reading the group of data from the first storage system, the data is validated by comparing the version checking data on the first storage system with version checking data on the second storage system.

Claims

1. A method comprising:

writing a block of data to a location on a first storage system;

writing version checking data associated with the block of data to the first storage system, wherein the version checking data has a predetermined initial value;

writing the version checking data associated with the block of data to a second storage system; and

upon subsequent writing of data to the location on the first storage system;

incrementing the version checking data on the first storage system; and

storing the incremented version checking data on the second storage system.

2. A method as recited in claim 1, further comprising writing checksum information associated with the block of data to the first storage system.

3. A method as recited in claim 1, wherein writing the block of data and writing the version checking data to the first storage system is performed in a single operation.

4. A method as recited in claim 1, wherein the first storage system is an array of disks.

5. A method as recited in claim 1, wherein the second storage system is a memory device in a storage controller coupled to the first storage system.

6. A method as recited in claim 1, wherein the second storage system is a non-volatile memory device.

7. A method as recited in claim 1, wherein the version checking data is a single bit of data.

8. A method comprising:

writing a block of data to a first location on a storage system;

writing version checking data associated with the block of data to the first location on the storage system, wherein the version checking data has a predetermined initial value;

writing the version checking data associated with the block of data to a second location on the storage system; and

upon subsequent writing of data to the location on the first storage system;

incrementing the version checking data stored at the first location on the storage system; and

storing the incremented version checking data at the second location on the storage system.

9. A method as recited in claim 8, wherein writing a block of data and writing version checking data associated with the block of data is performed in a single operation.

10. A method comprising:

reading data from a first storage system;

reading first version checking data from the first storage system, wherein the first version checking data is associated with the data read from the first storage system; and

validating the first version checking data with second version checking data stored on a second storage system.

11. A method as recited in claim 10, wherein validating the first version checking data includes:

reading second version checking data from a second storage system; and

determining whether the first version checking data matches the second version checking data.

12. A method as recited in claim 10, further comprising generating a version error message if the version checking data is not validated.

13. A method as recited in claim 10, further comprising initiating a data reconstruction process if the version checking data is not validated.

14. A method as recited in claim 10, further comprising reading checksum information from the first storage system, wherein the checksum information is associated with the data read from the first storage system.

15. A method as recited in claim 14, further comprising validating the checksum information using the data read from the first storage system.

16. A method as recited in claim 10, wherein the first storage system is a disk and the second storage system is a memory device in a storage controller coupled to the first storage system.

17. One or more computer-readable media having stored thereon a computer program that, when executed by one or more processors, causes the one or more processors to:

write a block of data to a location on a first storage system;

write version checking data to the first storage system, wherein the version checking data is associated with the block of data and has a predetermined initial value;

write the version checking data to a second storage system; and

upon subsequent writes of data to the location on the first storage system, increment the version checking data on the first storage system and store the incremented version checking data on the second storage system.

18. One or more computer-readable media as recited in claim 17, wherein the first storage system is a plurality of disks and the second storage system is a memory device.

19. One or more computer-readable media as recited in claim 17, wherein the block of data and the version checking data is written to the first storage system in a single operation.

20. An apparatus comprising:

a storage interface coupled to a plurality of storage devices;

version checking logic; and

a processor coupled to the storage interface and the version checking logic, wherein the processor is configured to read data from a first storage system and read first version checking data from the first storage system, wherein the first version checking data is associated with the data read from the first storage system, and wherein the processor is further configured to read second version checking data from a second storage system and validate the first version checking data with the second version checking data.

21. An apparatus as recited in claim 20, wherein the processor is configured to initiate a data reconstruction process if the version checking data is not validated.

22. An apparatus as recited in claim 20, wherein the second storage system is a memory device in a storage controller coupled to the first storage system.