Re: Debugging scsi abort handling ?

[Bart Van Assche <bvanassche@acm.org>]

On 08/25/14 10:47, Hans de Goede wrote:
> I want to see how real hardware deals with abort commands (e.g. does it
> only acknowledge the abort, or does it also sends a sense code for
> the actual command).

The SCSI specs define whether a reply should be sent if a SCSI command
has been aborted. From SAM-5: "5.3.1 Status codes [ ... ] TASK ABORTED.
This status shall be returned when a command is aborted by a command or
task management function on another I_T nexus and the Control mode page
TAS bit is set to one (see 5.6)."

"5.6 Aborting commands - A command is aborted when a SCSI device
condition (see 6.3), command, or task management function causes
termination of the command prior to its completion by the device server.
After a command is aborted and TASK ABORTED status, if any, is returned,
the SCSI target device shall send no further requests or responses for
that command."

>From SPC-4: "7.5.8 Control mode page [ ... ] A task aborted status (TAS)
bit set to zero specifies that aborted commands shall be terminated by
the device server without any response to the application client. A TAS
bit set to one specifies that commands aborted by the actions of an I_T
nexus other than the I_T nexus on which the command was received shall
be completed with TASK ABORTED status (see SAM-5)."

Bart.