Re: Error handling on FC devices

[Hannes Reinecke <hare@suse.de>]

On 11/29/2012 05:02 PM, James Smart wrote:
> Always possible - but....   Our f/w works at the FCP level and
> below, which means it doesn't know/do SCSI commands - e.g what the
> cdb within the FCP CMD frame is; know anything about SCSI device
> classes and state; etc. And it shouldn't be required to do so.
> Anytime this has been there in the past, it's been problematic.
>
> if we want to do this - we should add it to the midlayer/transport.
>
D'accord. Transport layer looks like a good fit.

What we should be doing is hooking up 'bus_reset' to be equivalent 
to REMOVE I_T NEXUS (SAS is already doing this).

In our case a REMOVE I_T NEXUS would be roughly equivalent to
scsi_remote_port_delete(); only we should be starting aborting
outstanding I/O directly and not waiting for fast_fail_tmo
to kick in.

I'll be posting a patch.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html