current multi-task abort model in RFC 3720

["T.Krishnanand" <krishnanand.thommandra@gmail.com>]

Folks,

I'm aware that a new multi-task model is being discussed on the mlist
these days. But the following questions are based on the CURRENT
RFC3720 model...and what initiators support TODAY.

Consider a scenario where multiple iSCSI initiators are sharing a
READ-ONLY (no SCSI reservations) access to a common LUN which has
advertized TAS=1 control mode page setting.

If LUN-reset from init-A and init-B happen on same lun then is it OK if
LUN-reset response to init-B TM cmd is sent AFTER "task aborted" scsi
status is sent to init-B for tasks aborted becoz of init-A's
LUN-reset.

IMHO after receiving the TM response wont init-B think that ALL
outstanding tasks are aborted and hence MAY be surprised to recv scsi
status for tasks which were outstanding when the LUN-reset was issued
from init-B.

IMHO think this scenario should be handled as follows, plz confirm if
my understanding is correct.

1)  start processing LUN-reset from init-A
2)  send TM response to init-A AFTER sending out "task aborted" scsi
status for tasks of init-B that were outstanding.
3) start processing LUN-reset from init-B. (At this time all init-B
tasks aborted by init-A's LUN-reset have been notified to the init-B).

Plz comment.

-tkrishna

_______________________________________________
Ips mailing list
Ips@ietf.org
https://www1.ietf.org/mailman/listinfo/ips