RE: iSCSI: underrun with a check condition

[Eddy Quicksall <eddyq@ivivity.com>]

Thanks,

That was my thinking too. And, according the 10.4.1, the U bit applies to
every status (BUSY, RESERVATION CONFLICT, etc). Agree?

I'm pointing this out so if there is someone out there that sees why 10.4.1
does not apply to every status, please give the case.

Eddy

-----Original Message-----
From: Santosh Rao [mailto:santoshr@cup.hp.com] 
Sent: Sunday, February 16, 2003 4:28 PM
To: eddyq@ivivity.com
Cc: ips@ece.cmu.edu
Subject: Re: iSCSI: underrun with a check condition

Eddy,

Yes, anytime the amount of data transferred does not match the data transfer
length specified, the target must set the U bit or O bit, depending on
whether
an underflow or overflow occurred.

A recovered error check condition may be returned as the response to a scsi
command which was processed to completion. The recovered error indicates
that a
previous command completed successfully with some recovery action by the
device
server and the sense data provides additional details on that previous
command.

The current command on which a recovered error check condition was returned
may
have been processed to completion, or experienced some underflow or
overflow.
This information must be conveyed by the target in the iscsi scsi response
pdu
using the appropriate fields to describe the underflow or overflow.

Thanks,
Santosh


> Should the target set the U bit when it gives a check condition to a
data-in
> command?
>  
>  
> Eddy