SCRUBBING PROCEDURE FOR A DATA STORAGE SYSTEM

• US 20110173162A1
• Filed: 01/14/2010
• Published: 07/14/2011
• Est. Priority Date: 01/14/2010
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Inventors: Wylie, John J., Li, Xiaozhou, Shah, Mehul A., Anderson, Eric A.
• Granted Patent: US 9,411,682 B2
• Time in Patent Office: Days
• US Class Current: 707/692
• 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/104 Metadata, i.e. metadata associated with RAID systems with parity
• CPC Class Codes: G06F 2211/1088 Scrubbing in RAID systems with parity

Abstract

A method is provided for scrubbing information stored in a data storage system where the information is stored as a plurality of encoded fragments across multiple storage devices. The method includes maintaining on a first storage device a list of metadata entries corresponding to values that are stored in the data storage system at an At Maximum Redundancy (AMR) state, verifying that encoded fragments associated with each of the metadata entries are stored on a second storage, verifying that a corresponding metadata entry is stored on the first storage device for each encoded fragment that is stored on the second storage device, and scheduling for recovery any missing encoded fragments and/or any missing metadata entry.

Claims

1. A method of scrubbing information stored in a data storage system, comprising:

maintaining on a first storage device a list of metadata entries corresponding to values that are stored in the data storage system at an At Maximum Redundancy (AMR) state;

verifying that encoded fragments associated with each of the metadata entries are stored on a second storage device;

verifying that a corresponding metadata entry is stored on the first storage device for each encoded fragment that is stored on the second storage device; and

scheduling for recovery any missing encoded fragments and/or any missing metadata entry.

2. The method as recited in claim 1, wherein scheduling for recovery comprises appending an entry corresponding to the missing fragment and/or missing metadata entry to a convergence log, and converging entries on the convergence log to an AMR state.

3. The method as recited in claim 1, further comprising determining whether each encoded fragment stored on the second storage device is a most recent version.

4. The method as recited in claim 3, further comprising removing from the second storage device any encoded fragment that is not the most recent version.

5. The method as recited in claim 1, further comprising determining whether a number of missing encoded fragments exceeds a threshold value, and, if so, accelerating recovery of the missing fragments.

6. The method as recited in claim 1, wherein the first and second storage devices are at a first storage location, and further comprising determining whether sibling fragments should be stored at a second storage location and, if so, transmitting a communication from the first storage location to the second storage location to cause the second storage location to verify that the sibling fragments are stored at the second storage location.

7. A method of scrubbing information stored as a plurality of encoded fragments across a plurality of storage nodes, comprising:

verifying, at a first storage node, that a plurality of encoded fragments associated with a plurality of values is stored at the first storage node;

scheduling any missing fragments for recovery by the first storage node;

transmitting a communication from the first storage node to a second storage node if the second storage node should have an encoded fragment that is a sibling of an encoded fragment stored at the first storage node;

in response to the communication, verifying, at the second storage node, that the sibling fragment is stored at the second storage node; and

if not, scheduling the sibling fragment for recovery by the second storage node.

8. The method as recited in claim 7, wherein metadata associated with the encoded fragments is stored at the first storage node, and wherein verifying comprises cross-checking the stored encoded fragments against the stored metadata.

9. The method as recited in claim 8, further comprising storing the plurality of encoded fragments on a first storage device at the first storage node, and storing the metadata on a second storage device at the first storage node.

10. The method as recited in claim 7, further comprising determining whether the encoded fragments are a most recent version.

11. The method as recited in claim 10, further comprising deleting any encoded fragments that are not the most recent version.

12. The method as recited in claim 8, wherein cross-checking comprises determining whether either a number of missing fragments or a number of missing metadata exceeds a threshold value, and, if so, accelerating recovery of the missing fragments and/or the missing metadata.

13. The method as recited in claim 7, wherein scheduling recovery comprises appending to a convergence log at the first storage location an entry corresponding to each missing fragment;

and converging, at the first storage location, the entries on the convergence log to an At Maximum Redundancy (AMR) state.

14. A data storage system, comprising:

a local storage node; and

a remote storage node in communication with the local storage node via a network, each of the local and remote storage nodes comprising;

a fragment server having a plurality of storage devices, each of the storage devices to store a plurality of encoded fragments and metadata associated with the encoded fragments, each of the

crosscheck the fragments stored on the fragment server'"'"'s storage devices against the metadata stored on the fragment server'"'"'s storage devices; and

schedule for recovery any fragments and/or metadata missing from the storage devices.

15. The system as recited in claim 14, wherein each fragment server is further configured to transmit messages to sibling fragment servers at the remote storage node to request that the sibling fragment servers verify storage of sibling fragments.

16. The system as recited in claim 14, wherein a first portion of the encoded fragments is stored on at first storage device at the local storage node, and wherein the metadata corresponding to the first portion is stored on a second storage device at the local storage node.

17. The system as recited in claim 14, wherein the fragment server is further configured to determine whether each stored fragment is a most recent version.

18. The system as recited in claim 17, wherein the fragment server is configured to delete from the storage devices any fragments that are not the most recent version.

19. The system as recited in claim 14, wherein the fragment server is configured to append to a convergence log an entry corresponding to a missing fragment and/or missing metadata to schedule the recovery.

20. The system as recited in claim 19, wherein the fragment server is configured to converge the entry in the convergence log to an At Maximum Redundancy (AMR) state.