Alberto Alonso wrote:
On Tue, 2007-10-23 at 18:45 -0400, Bill Davidsen wrote:
I'm not sure the timeouts are the problem, even if md did its own
timeout, it then needs a way to tell the driver (or device) to stop
retrying. I don't believe that's available, certainly not everywhere,
and anything other than everywhere would turn the md code into a nest of
exceptions.
If we loose the ability to communication to that drive I don't see it
as a problem (that's the whole point, we kick it out of the array). So,
if we can't tell the driver about the failure we are still OK, md could
successfully deal with misbehaved drivers.
I think what you really want is to notice how long the drive and driver
took to recover or fail, and take action based on that. In general "kick
the drive" is not optimal for a few bad spots, even if the drive
recovery sucks.
--
bill davidsen <davidsen@xxxxxxx>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
