FCP-3 Bridge Detection of FCP_DL error

Ralph Weber roweber at IEEE.org
Thu Jul 28 04:54:53 PDT 2005


* From the T10 Reflector (t10 at t10.org), posted by:
* Ralph Weber <roweber at ieee.org>
*
The FCP-3 WG minutes state that FCP-3 bridges are allowed to
detect FCP_DL errors after data has been transferred and that
in such cases that shall abort the command "with sense key set
to ABORTED COMMAND and ASC set to INVALID FIELD IN COMMAND
INFORMATION UNIT."

SPC-3 specifically states that the ABORTED COMMAND sense
key indicate the possibility that retrying the command will
correct the error. Maybe it will in this case, but probably
not.

I suggest that the HARDWARE ERROR sense key should at least
be considered by the FCP-3 WG as a replacement for ABORTED
COMMAND in this case. SPC-3 lists examples of reasons for
using HARDWARE ERROR and the examples include parity errors.
It seems to me that the FCP_DL problem has enough in common
with parity errors that the HARDWARE ERROR would be okay
in this case.

All the best,

.Ralph

*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org





More information about the T10 mailing list