RAID STORAGE REBUILD PROCESSING

• US 20140215147A1
• Filed: 01/25/2013
• Published: 07/31/2014
• Est. Priority Date: 01/25/2013
• Status: Abandoned Application

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Pan, Weimin
• Application Number:
  US13/750,896
• Publication Number:
  US 20140215147A1
• Time in Patent Office: Days
• US Class Current: 711/114
• CPC Class Codes: G06F 11/1092 Rebuilding, e.g. when physically replacing a failing disk

Abstract

A storage management module configured to identify storage volumes to be rebuilt and remaining storage volumes that are not to be rebuilt, calculate rebuild priority information for the identified storage volumes to be rebuilt based on storage information of the identified storage volumes, and generate rebuild requests to rebuild the identified storage volumes to be rebuilt and process host requests directed to the remaining and to be rebuilt storage volumes based on the rebuild priority information and amount of host requests, wherein with relative high amount of host requests, generate relative less rebuild requests but not less than a minimum rebuild traffic percentage or more than a maximum rebuild traffic percentage.

Claims

1. A redundant array of independent disks (RAID) storage system comprising:

a storage controller with a storage management module to;

identify storage volumes to be rebuilt and remaining storage volumes that are not to be rebuilt,

calculate rebuild priority information for the identified storage volumes to be rebuilt based on storage information of the identified storage volumes, and

generate rebuild requests to rebuild the identified storage volumes to be rebuilt and process host requests directed to the remaining and to be rebuilt storage volumes based on the rebuild priority information and amount of host requests, wherein with relative high amount of host requests, generate relative less rebuild requests but not less than a minimum rebuild traffic percentage or more than a maximum rebuild traffic percentage.

2. The storage system of claim 1, wherein the storage management module is further configured to calculate rebuild priority information based on storage information that includes at least one of fault tolerance state based on RAID level of the storage volumes and the number of failed status storage devices, number of predictive failure status storage devices of storage volumes, estimated rebuild time to rebuild storage volumes, number of storage devices of storage volumes, and type of storage devices of storage volumes.

3. The storage system of claim 1, wherein the storage management module is further configured to generate rebuild requests that include requests to rebuild data from non failure storage devices of the identified storage volumes to spare storage devices.

4. The storage system of claim 1, wherein the storage management module is further configured to process host requests that include to process host requests from a host to read data from storage devices of storage volumes and write data to storage devices of storage volumes.

5. The storage system of claim 1, wherein the storage management module is further configured to identify storage volumes to be rebuilt include to identify storage devices of the storage volumes that have a failed status or a predictive failure status.

6. The storage system of claim 1, wherein the storage management module is further configured to adjust number of rebuild requests based on rebuild priority information and host requests.

7. The storage system of claim 1, wherein the storage management module is further configured to assign storage volumes a minimum rebuild traffic percentage and a maximum rebuild traffic percentage based on associated rebuild priority information, and to assign a relative high minimum rebuild traffic percentage to storage volumes with relative high rebuild priority information.

8. The storage system of claim 1, wherein if amount complete of a first priority rebuild is less than a completion percentage, stop the first priority rebuild and start a second priority rebuild having a higher priority than the first rebuild otherwise continue with the first priority rebuild.

9. A method for processing storage, the method comprising:

identifying, by a storage management module, storage volumes to be rebuilt and remaining storage volumes that are not to be rebuilt;

calculating, by the storage management module, rebuild priority information for the identified storage volumes to be rebuilt based on storage information of the identified storage volumes; and

generating, by the storage management module, rebuild requests to rebuild the identified storage volumes to be rebuilt and processing host requests directed to the remaining and to be rebuilt storage volumes based on the rebuild priority information and amount of host requests, wherein with relative high amount of host requests, generating relative less rebuild requests but not less than a minimum rebuild traffic percentage or more than a maximum rebuild traffic percentage.

10. The method of claim 9, wherein the storage management module further configured for calculating rebuild priority information based on storage information that includes at least one of fault tolerance state based on RAID level of the storage volumes and the number of failed status storage devices, number of predictive failure status storage devices of storage volumes, estimated rebuild time to rebuild storage volumes, number of storage devices of storage volumes, and type of storage devices of storage volumes.

11. The method of claim 9, wherein the storage management module is further configured for generating rebuild requests that include requests for rebuilding data from non failure storage devices of the identified storage volumes to spare storage devices.

12. The method of claim 9, wherein the storage management module is further configured for processing host requests that include processing host requests from a host for reading data from storage devices of storage volumes and writing data to storage devices of storage volumes.

13. The method of claim 9, wherein the storage management module is further configured for adjusting number of rebuild requests based on rebuild priority information and host requests.

14. The method of claim 9, wherein the storage management module is further configured for generating rebuild requests and host requests to include assigning storage volumes a minimum rebuild traffic percentage and a maximum rebuild traffic percentage based on associated rebuild priority information, and to assign a relative high minimum rebuild traffic percentage to storage volumes with relative high rebuild priority information.

15. A non-transitory computer-readable medium having computer executable instructions stored thereon to process storage, the instructions are executable by a processor to:

identify storage volumes to be rebuilt and storage volumes that are not to be rebuilt;

calculate rebuild priority information for the identified storage volumes to be rebuilt based on storage information of the identified storage volumes; and

generate rebuild requests to rebuild the identified storage volumes to be rebuilt and process host requests directed to the remaining and to be rebuilt storage volumes based on the rebuild priority information and amount of host requests, wherein with relative high amount of host requests, generate relative less rebuild requests but not less than a minimum rebuild traffic percentage or more than a maximum rebuild traffic percentage.

16. The non-transitory computer readable medium of claim 15, further comprising instructions to cause the processor to calculate rebuild priority information based on storage information that includes at least one of fault tolerance state based on RAID level of the storage volumes and the number of failed status storage devices, number of predictive failure status storage devices of storage volumes, estimated rebuild time to rebuild storage volumes, number of storage devices of storage volumes, and type of storage devices of storage volumes.

17. The non-transitory computer readable medium of claim 15, further comprising instructions to cause the processor to rebuild requests that include requests to rebuild data from non failure storage devices of the identified storage volumes to spare storage devices.

18. The non-transitory computer readable medium of claim 15, further comprising instructions to cause the processor to process host requests that include to process host requests from a host to read data from storage devices of storage volumes and write data to storage devices of storage volumes.

19. The non-transitory computer readable medium of claim 15, further comprising instructions to cause the processor to adjust number of rebuild requests based on rebuild priority information and host requests.

20. The non-transitory computer readable medium of claim 15, further comprising instructions to cause the processor to assign storage volumes a minimum rebuild traffic percentage and a maximum rebuild traffic percentage based on associated rebuild priority information, and to assign a relative high minimum rebuild traffic percentage to storage volumes with relative high rebuild priority information.