1 |
On Thu, Oct 6, 2011 at 1:28 PM, Michael Mol <mikemol@×××××.com> wrote: |
2 |
> On Thu, Oct 6, 2011 at 4:21 PM, Mark Knecht <markknecht@×××××.com> wrote: |
3 |
>> On Thu, Oct 6, 2011 at 1:03 PM, Paul Hartman |
4 |
>> My worry was that if the mdraid daemon saw one drive gone - either |
5 |
>> when starting to spin down or when one spins up slowly - and if mdraid |
6 |
>> didn't understand that all this stuff was taking place intentionally |
7 |
>> then it might mark that drive as having failed. |
8 |
> |
9 |
> Does mdraid even have an awareness of timeouts, or does it leave that |
10 |
> to lower drivers? I think the latter condition is more likely. |
11 |
> |
12 |
> I suspect, though, that if your disk fails to spin up reasonably |
13 |
> quickly, it's already failed. |
14 |
> |
15 |
|
16 |
In general I agree. However drives that are designed for RAID have a |
17 |
feature known as Time Limited Error Recovery (TLER) which supposedly |
18 |
guarantees that they'll get the drive back to responding fast enough |
19 |
to not have it marked as failed in the RAID array: |
20 |
|
21 |
http://en.wikipedia.org/wiki/Time-Limited_Error_Recovery |
22 |
|
23 |
When I built my first RAID I bought some WD 1TB green drives, built |
24 |
the RAID and immediately had drives failing because they didn't have |
25 |
this sort of feature. I replaced them with RAID Edition drives that |
26 |
have the TLER feature and have never had a problem since. (Well, I |
27 |
actually bought all new drives and kept the six 1TB drives which I'd |
28 |
mostly used up for other things like external eSATA backup drives, |
29 |
etc...) |
30 |
|
31 |
Anyway, I'm possibly over sensitized to this sort of timing problem |
32 |
specifically in a RAID which is why I asked the question of Paul in |
33 |
the first place. |
34 |
|
35 |
Cheers, |
36 |
Mark |