IP Library › Granted Patent US 8,185,784
Granted Patent B2
US 8,185,784 · App. 12/150,426 · Granted May 22, 2012

Drive health monitoring with provisions for drive probation state and drive copy rebuild

Assignee: LSI Corporation
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,185,784
App. No.
12/150,426
Granted
May 22, 2012
Kind
B2
Abstract

The present disclosure is directed to a system and method for monitoring drive health. A method for monitoring drive health may comprise: a) conducting a predictive fault analysis for at least one drive of a RAID; and b) copying data from the at least one drive of the RAID to a replacement drive according to the predictive fault analysis. A system for monitoring drive health may comprise: a) means for conducting a predictive fault analysis for at least one drive of a RAID; and b) means for copying data from the at least one drive of the RAID to a replacement drive according to the predictive fault analysis.

Claims (51)

1. A system comprising:

means for conducting a predictive fault analysis for at least one drive of a redundant array of independent drives (RAID), wherein the means for conducting a predictive fault analysis for at least one drive of a redundant array of independent drives (RAID) comprises:

means for computing a drive-reliability metric for the at least one drive of the RAID, wherein the means for computing a drive-reliability metric for the at least one drive of the RAID comprises:

means for disregarding at least a portion of the drive-reliability metric according to an IO channel disturbance independent of the function of the at least one drive of the RAID; and

means for copying data from the at least one drive of the RAID to a replacement drive when the number of times the drive reliability metric passes the first threshold value passes a second threshold value.

2. The system of claim 1 , wherein the means for computing a drive-reliability metric for the at least one drive of the RAID comprises:

means for computing a time between an input/output (IO) request and a completion of the IO request.

3. The system of claim 1 , wherein the means for computing a drive-reliability metric for the at least one drive of the RAID comprises:

means for computing a time between a completion of a first input/output (IO) request and a completion of a second IO request.

4. The system of claim 1 , wherein the means for computing a drive-reliability metric for the at least one drive of the RAID comprises:

means for comparing the drive reliability metric to a rate-based threshold value.

5. The system of claim 1 , wherein the means for computing a drive-reliability metric for the at least one drive of the RAID comprises:

means for comparing the drive reliability metric to a user-defined threshold value.

6. The system of claim 1 , wherein the means for disregarding at least a portion of the drive-reliability metric according to an IO channel disturbance independent of the function of the at least one drive of the RAID comprises:

means for disregarding at least a portion of the drive-reliability metric according to an IO channel disturbance associated with at least one of a channel initialization, a channel communication disruption, or a channel exception that delays completion of an IO request.

7. The system of claim 1 , further comprising:

means for redirecting IO requests addressed to the at least one drive in the RAID to the replacement drive.

8. The system of claim 1 , further comprising:

means for reconstructing data of the at least one drive in the RAID from the replacement drive.

9. The system of claim 1 , further comprising:

means for storing at least one of RAID state data, RAID control data, or RAID configuration data to a non-RAID drive.

10. The system of claim 1 , further comprising:

means for verifying at least one of a read or write operation to the at least one drive of the RAID utilizing redundant RAID data.

11. A computer-readable medium comprising computer readable instructions for execution on a processor which, when executed on a processor, cause a computing device to execute a process, the process comprising:

conducting a predictive fault analysis for at least one drive of a redundant array of independent drives (RAID), wherein the conducting a predictive fault analysis for at least one drive of a redundant array of independent drives (RAID) comprises:

computing a drive-reliability metric for the at least one drive of the RAID, wherein the computing a drive-reliability metric for the at least one drive of the RAID comprises:

means for disregarding at least a portion of the drive-reliability metric according to an IO channel disturbance independent of the function of the at least one drive of the RAID; and

copying data from the at least one drive of the RAID to a replacement drive when the number of times the drive reliability metric passes the first threshold value passes a second threshold value.

12. A method comprising:

conducting a predictive fault analysis for at least one drive of a redundant array of independent drives (RAID), wherein the conducting a predictive fault analysis for at least one drive of a redundant array of independent drives (RAID) comprises:

computing a drive-reliability metric for the at least one drive of the RAID, wherein the computing a drive-reliability metric for the at least one drive of the RAID comprises:

disregarding at least a portion of the drive-reliability metric according to an 10 channel disturbance independent of the function of the at least one drive of the RAID; and

copying data from the at least one drive of the RAID to a replacement drive when the number of times the drive reliability metric passes the first threshold value passes a second threshold value.

13. The method of claim 12 , wherein the computing a drive-reliability metric for the at least one drive of the RAID comprises:

computing a time between an input/output (IO) request and a completion of the IO request.

14. The method of claim 12 , wherein the computing a drive-reliability metric for the at least one drive of the RAID comprises:

computing a time between a completion of a first input/output (IO) request and a completion of a second IO request.

15. The method of claim 12 , wherein the computing a drive-reliability metric for the at least one drive of the RAID comprises:

comparing the drive reliability metric to a rate-based threshold value.

16. The method of claim 12 , wherein the computing a drive-reliability metric for the at least one drive of the RAID comprises:

comparing the drive reliability metric to a user-defined threshold value.

17. The method of claim 12 , wherein the disregarding at least a portion of the drive-reliability metric according to an IO channel disturbance independent of the function of the at least one drive of the RAID comprises:

disregarding at least a portion of the drive-reliability metric according to an IO channel disturbance associated with at least one of a channel initialization, a channel communication disruption, or a channel exception that delays completion of an IO request.

18. The method of claim 12 , further comprising:

redirecting IO requests addressed to the at least one drive in the RAID to the replacement drive.

19. The method of claim 12 , further comprising:

reconstructing data of the at least one drive in the RAID from the replacement drive.

20. The method of claim 12 , further comprising:

storing at least one of RAID state data, RAID control data, or RAID configuration data to a non-RAID drive.

21. The method of claim 12 , further comprising:

verifying at least one of a read or write operation to the at least one drive of the RAID utilizing redundant RAID data.

Assignments (8)
CORRECTIVE ASSIGNMENT TO CORRECT THE EFFECTIVE DATE OF MERGER TO 09/05/2018 PREVIOUSLY RECORDED AT REEL: 047230 FRAME: 0133. ASSIGNOR(S) HEREBY CONFIRMS THE MERGER. Recorded Oct 29, 2018
From: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.
To: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITED
Reel/Frame 047630/0456 →
MERGER Recorded Oct 4, 2018
From: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.
To: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITED
Reel/Frame 047230/0133 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Feb 3, 2017
From: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
To: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.
Reel/Frame 041710/0001 →
PATENT SECURITY AGREEMENT Recorded Feb 11, 2016
From: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 037808/0001 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS (RELEASES RF 032856-0031) Recorded Feb 2, 2016
From: DEUTSCHE BANK AG NEW YORK BRANCH, AS COLLATERAL AGENT
To: LSI CORPORATION; AGERE SYSTEMS LLC
Reel/Frame 037684/0039 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 3, 2015
From: LSI CORPORATION
To: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.
Reel/Frame 035390/0388 →
PATENT SECURITY AGREEMENT Recorded May 8, 2014
From: LSI CORPORATION; AGERE SYSTEMS LLC
To: DEUTSCHE BANK AG NEW YORK BRANCH, AS COLLATERAL AGENT
Reel/Frame 032856/0031 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 28, 2008
From: MCCOMBS, CRAIG C.; NAIR, NAMAN; JESS, MARTIN; BIRZER, JEREMY
To: LSI CORPORATION
Reel/Frame 020912/0268 →
Continuity (1)
Related Publication 20090271657A1 · Oct 29, 2009