Re: iSCSI:Intent of sec. 8.4 of draft 07-95

["Mallikarjun C." <cbm@rose.hp.com>]

Barry,

Let me comment on your question.

A lost status PDU causes more than a SCSI timeout to the 
concerned task!  A lost status creates a gap in the StatSN space
that prevents the initiator to acknowledge any StatSNs after
the gap.  Either the lost status has to be recovered, or the
connection has to be done away with - that's what the quoted
text is describing.

Please refer to the following URL and its related thread for 
additional discussion on the editing philosophy behind error 
recovery details in the draft - specifically the internal 
implementation Vs on-the-wire aspects of error recovery.

http://www.pdl.cmu.edu/mailinglists/ips/mail/msg06564.html

Regards.
-- 
Mallikarjun 


Mallikarjun Chadalapaka
Networked Storage Architecture
Network Storage Solutions Organization
MS 5668 Hewlett-Packard, Roseville.
cbm@rose.hp.com


Barry Reinhold wrote:
> 
> Clause 8.4 states:
> 
> "- If the discarded PDU is a response PDU, initiator MUST do
>              one of the following -
>                        a) Request PDU retransmission with a status SNACK.
>                           [OR]
>                        b) Logout the connection for recovery and continue
>                           the tasks on a different connection instance as
>                           described in section 7.1. [OR]
>                        c) Logout to close the connection (abort all the
>                           commands associated with the connection) "
> 
> Is it the intent of the draft to eliminate the action of just dropping the
> PDU. (i.e. allowing error recovery by having a SCSI timeout?)
> 
> Barry Reinhold
> Principal Architect
> Trebia Networks
> barry.reinhold@trebia.com
> 603-868-5144/603-659-0885/978-929-0830 x138