Data Out residual overflow/underflow handling
phughes at solidfire.com
Fri Sep 21 09:02:28 PDT 2012
Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1209210_f.htm">HTML-formatted message</a>
I recently posed this question to the IETF's IP Storage mailing list
(iSCSI), but thought I'd get some opinions from T10 as well.
How should an iSCSI target (SCSI direct-access block device) handle the
An initiator issues an iSCSI Command Request PDU containing a SCSI Write
CDB with a transfer length of 1 block. The iSCSI Command Request PDU has
an Expected Data Transfer Length of 512 bytes, a Data Segment Length of 512
bytes (immediate data), and the Final flag is set. This would be a
perfectly normal single block write, except that the target's logical unit
is formatted with 4096-byte block size. So it appears the initiator is
confused and sending a single 512-byte block write to a logical unit that
is formatted to 4KB block size.
Here are my thoughts:
1) The target could write the 512 bytes of immediate data plus 3584 bytes
(4096 minus 512) of whatever it wants to the media, and then send an iSCSI
Command Response PDU with SCSI status of Good and reporting an Overflow
with a residual count of 3584. This seems to be the most correct way of
handling this scenario, but it seems dangerous to allow an apparently
confused initiator to essentially corrupt data on the logical unit.
2) The target could send an iSCSI Command Response PDU with SCSI status of
Check Condition, with sense data of Aborted Command, Invalid Field in
Command Information Unit (0x0E03). This sense code is apparently intended
for FCP (I found it mentioned in FCP-4) but it seems appropriate in this
Are there any other alternatives?
More information about the T10