<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.ietf.ips">
    <title>gmane.ietf.ips</title>
    <link>http://blog.gmane.org/gmane.ietf.ips</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.ips/6130"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.ips/6129"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.ips/6127"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.ips/6124"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.ips/6123"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.ips/6117"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.ips/6116"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.ips/6114"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.ips/6112"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.ips/6110"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.ietf.ips/6108"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.ips/6130">
    <title>Data Out residual overflow/underflow handling</title>
    <link>http://comments.gmane.org/gmane.ietf.ips/6130</link>
    <description>&lt;pre&gt;Not sure if this is the best place to ask, but here goes...

How should an iSCSI target (SCSI direct-access block device) handle the
following scenario:

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
case.  Assuming the target can fail the SCSI Write command this way (or
some other way), should the target also report an Underflow with a residual
count of 512?

Are there any other alternatives?

Thanks,
Paul
_______________________________________________
Ips mailing list
Ips&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/ips
&lt;/pre&gt;</description>
    <dc:creator>Paul Hughes</dc:creator>
    <dc:date>2012-09-21T03:21:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.ips/6129">
    <title>about iSCSI TEXT negotiation</title>
    <link>http://comments.gmane.org/gmane.ietf.ips/6129</link>
    <description>&lt;pre&gt;Hi dear all,
Please think about the following sequence
I-&amp;gt;TEXT,C=1,F=0
T-&amp;gt;TEXT,C=x,F=0,DataSegmentLength=0
What is the valid target response ?
Does the value of x matter ?
or just DataSegmentLength=0 is enough ?
Many thanks .
_______________________________________________
Ips mailing list
Ips&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/ips

&lt;/pre&gt;</description>
    <dc:creator>yushang</dc:creator>
    <dc:date>2012-03-30T17:44:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.ips/6127">
    <title>data exceeds MaxBurstLength</title>
    <link>http://comments.gmane.org/gmane.ietf.ips/6127</link>
    <description>&lt;pre&gt;Hi dear all,
If the transmitter (initiator or target) transfer some data exceeds the value
MaxBurstLength specified . What shold happen ? It seems rfc3720 do
not provide a clause for this situation . Thanks in advance .
_______________________________________________
Ips mailing list
Ips&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/ips

&lt;/pre&gt;</description>
    <dc:creator>yushang</dc:creator>
    <dc:date>2012-03-29T15:17:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.ips/6124">
    <title>iSCSI WRITE (10)</title>
    <link>http://comments.gmane.org/gmane.ietf.ips/6124</link>
    <description>&lt;pre&gt;Hi,

Ok I'm a lot further: the whole discovery handshake (including mode
sense, inquiries and what not) works find. Small reads/writes work too
(the ones with data in the pdu message).

Something which is not entirely clear from the RFC is the following:
- an initiator sends a 0x05 PDU (data-out) with data to be stored on
  disk.
  after processing, the target should send back a 0x21 PDU (scsi
  response). is that correct?



Folkert van Heusden

&lt;/pre&gt;</description>
    <dc:creator>folkert</dc:creator>
    <dc:date>2011-02-09T17:18:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.ips/6123">
    <title>SCSI inquire command &amp; iscsi wrapping</title>
    <link>http://comments.gmane.org/gmane.ietf.ips/6123</link>
    <description>&lt;pre&gt;Hi,

I'm struggling to get scsi 0x12 command working in my iSCSI target
(which will be an opensource java iSCSI target by the way).

I follow the procedure as described at
http://en.wikipedia.org/wiki/SCSI_Inquiry_Command

If I understand it correctly this is what happens:
Now, I receive an PDU with opcode 0x01 (SCSI command). In it, there's
the CDB with byte 3 and 4 telling how much extra data (apart from the
regular 16 CDB in the PDU) may be send by the target.
So as a target, let's say cdb byte 3+4 tell me i can send 'x' bytes.
So in the CDB space in the PDU I put a CDB with opcode 12 and byte 3+4
telling how many bytes I want to send.
Then, of the next 36 bytes I would want to send (I don't have any vendor
specific data), I can add 'x' bytes after the PDU with byte 4 set to
MIN(x, 36) - 4.

My question now is: am I right?


Folkert van Heusden

&lt;/pre&gt;</description>
    <dc:creator>folkert</dc:creator>
    <dc:date>2011-02-02T14:13:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.ips/6117">
    <title>this list</title>
    <link>http://comments.gmane.org/gmane.ietf.ips/6117</link>
    <description>&lt;pre&gt;Hi,

Is this list available for generic iSCSI questions?

If so: some (linux iscsi target and window iStorageSErver) respond with
valid data to Read Capacity(10) SCSI 0x25 command while for example
nexenta store (an opensolaris system) responds with Check Condition.
So I guess this is not the common way of determing the sector size and
size of the device.
Which command should I use for this?
Thanks.


Folkert van Heusden

&lt;/pre&gt;</description>
    <dc:creator>folkert</dc:creator>
    <dc:date>2011-01-24T13:30:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.ips/6116">
    <title>Contribution to ISCSI in opensource</title>
    <link>http://comments.gmane.org/gmane.ietf.ips/6116</link>
    <description>&lt;pre&gt;_______________________________________________
Ips mailing list
Ips&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/ips
&lt;/pre&gt;</description>
    <dc:creator>mandar sawant</dc:creator>
    <dc:date>2010-06-18T06:11:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.ips/6114">
    <title>Data Segment Padding</title>
    <link>http://comments.gmane.org/gmane.ietf.ips/6114</link>
    <description>&lt;pre&gt;_______________________________________________
Ips mailing list
Ips&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/ips
&lt;/pre&gt;</description>
    <dc:creator>yushang</dc:creator>
    <dc:date>2009-10-09T03:33:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.ips/6112">
    <title>Data-In ExpDataSN</title>
    <link>http://comments.gmane.org/gmane.ietf.ips/6112</link>
    <description>&lt;pre&gt;_______________________________________________
Ips mailing list
Ips&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/ips
&lt;/pre&gt;</description>
    <dc:creator>yushang</dc:creator>
    <dc:date>2009-09-25T06:30:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.ips/6110">
    <title>iSCSI RW Command</title>
    <link>http://comments.gmane.org/gmane.ietf.ips/6110</link>
    <description>&lt;pre&gt;_______________________________________________
Ips mailing list
Ips&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/ips
&lt;/pre&gt;</description>
    <dc:creator>yushang</dc:creator>
    <dc:date>2009-09-22T04:34:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.ietf.ips/6108">
    <title>lun reset and r2t error handling</title>
    <link>http://comments.gmane.org/gmane.ietf.ips/6108</link>
    <description>&lt;pre&gt;Hi,

For a single connection session with ERL=0 and without FastAbort, if the 
initiator has sent a lun reset task management function and the target 
has sent a R2T, is it ok for the target to send a task management 
response with Function Complete, before the initiator has sent the 
data-out pdus for the R2T? It looks like the reason the target will do 
this is due to a internal target timeout (target did not get the 
data-outs within some timeout period).

If the target does return the task management function with Function 
Complete, should the initiator continue to respond to the R2Ts?

And one other question. In section 10.5.1, we have:

    The issuing initiator SHOULD however terminate (i.e., by setting the
    F-bit to 1) these response sequences as quickly as possible.

Does this mean if we have sent a lun reset, and the target has sent a 
R2T, should we be setting the F-bit in the continued data-out PDU so as 
to end the transfer, even though actual data transfer has not been 
completed entirely?

What if we do send all the data like normal, should that still be ok?
_______________________________________________
Ips mailing list
Ips&amp;lt; at &amp;gt;ietf.org
https://www.ietf.org/mailman/listinfo/ips

&lt;/pre&gt;</description>
    <dc:creator>Mike Christie</dc:creator>
    <dc:date>2009-08-11T20:56:10</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.ietf.ips">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.ietf.ips</link>
  </textinput>
</rdf:RDF>
