QUESTION: writesame10, dif2, ato=1, wrprotect=0 ref tag

Gerry Houlder gerry.houlder at seagate.com
Mon Feb 7 09:44:22 PST 2011


Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1102070_f.htm">HTML-formatted message</a>

For this case, WRITE SAME acts the same as WRITE. The Reference Tag is
filled with 0xFFFF_FFFF.
On Thu, Feb 3, 2011 at 3:08 PM, scott taggart <scott.taggart at oakgatetech.com
> wrote:
> * From the T10 Reflector (t10 at t10.org), posted by:
> * scott taggart <scott.taggart at oakgatetech.com>
> *
> Hi,
>
> SBC3R24, table 108 (WriteSame10, LBDATA=0, PBDATA=0) states:
> If the medium is formatted with type 1 or type 2 protection information,
> then:
> a) The device server shall place the value from each LOGICAL BLOCK
> REFERENCE TAG field received in the single block of data from the data-out
> buffer into the corresponding LOGICAL BLOCK REFERENCE TAG field of the
> first logical block written to the medium. The device sever shall place the
> value of the previous LOGICAL BLOCK REFERENCE TAG field plus one into
> each of the subsequent LOGICAL BLOCK REFERENCE TAG fields;
> My question is what value does the target write for the REF tag in
> DIF2 mode, ATO=1, wrprotect=0 for WriteSame10.  Does it write the LBA
> value or 0xFFFFFFFF?	 If it behaves like a write10, it would be
> 0xFF... but the spec seems just vague enough to allow the LBA value
> from the CDB to be used.  Can someone please clarify.
>
> Thanks,
>
> Scott
>
> *
> * For T10 Reflector information, send a message with
> * 'info t10' (no quotes) in the message body to majordomo at t10.org
>



More information about the T10 mailing list