On Sun, 2013-11-17 at 11:15 -0500, Phillip Susi wrote:
> On 11/17/2013 01:43 AM, James Bottomley wrote:
> > OK, so three people have now told you that's not how the code
> > works. Why don't you just read it? because there's not really much
> > point us reading your patches until you do.
>
> I have, which is why I said it handles it via scsi_eh_stu. If I'm not
> understanding it correctly, then by all means, explain.
Because you don't damn well listen. Two emails ago I said:
The error handler is not automatically activated for a not
ready/initializing command required because of multi-path
I don't really understand how I can be clearer. You keep wittering
about the error handler spin up but if the error handler doesn't
activate, the disk is never spun up with your patch. This is the
problem we keep telling you about. You can't make the error handler
always activate because then multi-path would fail.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
