Error in the published version of SAT-2 --- 4K alignment impact

Mark Overby MOverby at nvidia.com
Wed Feb 10 08:33:46 PST 2010


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

That one has already been reported and will be fixed in r1 of SAT-3 (issue
#1)
Issue #2 is the subject of some debate. If someone wishes to take a stab at
it, they should bring in a proposal against SAT-3.
On 2/10/10 12:33 AM, "Nilesh Govande" <nileshgovande at gmail.com> wrote:
* From the T10 Reflector (t10 at t10.org), posted by:
* Nilesh Govande <nileshgovande at gmail.com>
*
Following the same thread, I would like to report following errors in
SAT2R09 (Rev 16 Sept 2009)
1)As per SAT2R09 section 12.5.1.1.2 SECURITY PROTOCOL IN parameter data,
"The SATL shall set the MASTER PASSWORD IDENTIFIER field to the ATA
IDENTIFY DEVICE data word 82."
Whereas, As per ATA8  - IDENTIFY DEVICE DATA, word 92 carries master
password identifier.
2)SAT standard should make a concrete statement somewhere about how to
process ATA pass through command under purview of
		1) Persistent reservations.
		2) Security IN / OUT - SAT extension under varius
security states.
	     (Or at least should clearly say that the behavior under
the two conditions is vendor specific)
Nilesh
On Wed, Feb 10, 2010 at 5:49 AM, James C Hatfield
<james.c.hatfield at seagate.com> wrote:
> All,
>
> I just discovered an error in SAT-2 that was not caught in letter ballot
> reviews.
> Mark Overby checked and it is in the official ANSI revision as well.
>
> We need to fix it in SAT-3, and (most importantly)
> *  anyone who implements multiple logical sectors per physical sector
(e.g.,
> 4K emulation) should be aware of the error
>
> ========================================================================
> Reference:
>	SAT2R09 	16 September 2009	  T10/1826-D Revision 09
>	Section 5.7, Figure 8
>	     (The upper part of Figure 8 - <<not the lower part of Figure
8>>)
> ========================================================================
> Figure 8 - Logical Sector Alignment Examples (part 1 of 3)
>
> ATA: LOGICAL SECTORS PER PHYSICAL SECTOR field set to 1h
> SCSI: LOGICAL BLOCKS PER PHYSICAL BLOCK field set to 1h
>
> (indicating 21 logical blocks per physical block):
> ATA: LOGICAL SECTOR ALIGNMENT field set to 1h:
> SCSI: LOWEST ALIGNED LOGICAL BLOCK ADDRESS field set to 1h:
> ========================================================================
>
> ========================================================================
> Corrections needed:
> ========================================================================
>   a) the LOGICAL SECTOR ALIGNMENT field			      should
> be 0h (not 1h)
>   b) the LOWEST ALIGNED LOGICAL BLOCK ADDRESS field	 should be 0h (not
1h)
>
>
> Thank You !!!
> -----------------------------------------------------------------
> Jim Hatfield
> Seagate Technology LLC
>   e-mail:  James.C.Hatfield at seagate.com
>   s-mail:  389 Disc Drive;  Longmont, CO 80503 USA
>   voice:  720-684-2120
>   fax....: 720-684-2766
>
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org
-----------------------------------------------------------------------------
------
This email message is for the sole use of the intended recipient(s) and may
contain
confidential information.  Any unauthorized review, use, disclosure or
distribution
is prohibited.	If you are not the intended recipient, please contact the
sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------
------



More information about the T10 mailing list