On Tue, Sep 03, 2002 at 09:35:02AM -0500, James Bottomley wrote:
>
> 1) Quiesce host (set in_recovery flag)
Right.
> 2) Suspend active timers on this host
Right.
> 3) Proceed down the error correction track (eliminate abort and go down
> device, bus and host resets and finally set the device offline).
Leave abort active. It does actually work in certain scenarios. The CD
burner scenario that started this thread is an example of somewhere that
an abort should actually do the job.
> 5) On each error recovery wait out a recovery timer for the device to become
> active before talking to it again. Send all affected commands back to the
> block layer to await reissue (note: it would now be illegal for commands to
> lie to the mid layer and say they've done the reset when they haven't).
> 6) issue a TUR using a command allocated to the eh for that purpose. Process
> the return code (in particular, if the device says NOT READY, wait some more).
> Only if the TUR definitively fails proceed up the recovery chain all the way
> to taking the device offline.
Right.
> I also plan to expose the suspend and resume timers API in some form for FC
> drivers to use.
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Sep 07 2002 - 22:00:18 EST