Hello, Mark.
Mark Lord wrote:
Sure it does. It can determine the number of consecutive failures on
the same drive/channel, and it can also count intervening successes, if any.
From that, at a minimum, it could notice that the same drive has gone 'round
the error treadmill (say) 20 times in a row, with no other I/O possible on it
because it has yet to successfully complete the reset+reinit phase.
If a device fails reset+reinit phase a few times, libata surely drops
the device, but I don't think the kernel can drop a device because it
failed, say, 20 consecutive IO commands when it can respond to reset and
reinit. That's where policy needs to come in, IMHO.
For Ric's case, I'm waiting for more info. If EH is looping forever
without reporting to upper layer, it definitely needs fixing, but I
don't think that's the case.
Such a drive is a candidate for pushing the error upstairs,
and possibly for getting offlined.
Fancier fault-handling is also possible, but the bare minimum is that we
must not get stuck forever looping in the EH code. Eventually a failed
status
has to be returned to the layers above, I think.
Error is always pushed upstairs. libata itself doesn't initiate any
kind of retrials. That's upto high level driver - in this case, sd.
One of the problems is that currently libata EH can take some minutes
recovering from an error condition. With partial request retry from sd,
a batch of consecutive bad sectors can make recovery take a really
long time. This needs fixing.
Thanks.
--
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
