Seagate Comments on SSC-2R3 and 01-146

Paul.A.Suhler at seagate.com Paul.A.Suhler at seagate.com
Tue Jun 26 09:52:16 PDT 2001


* From the T10 Reflector (t10 at t10.org), posted by:
* Paul.A.Suhler at seagate.com
*
Folks,

Since some companies will not be represented at the 16 July working group,
I'm posting these comments to the reflector, in addition to sending them to
Dave Peterson.

I've deleted from this e-mail some Editorial comments that shouldn't need
discussion.

The Technical comments include making uniform across commands the alignment
of 8-byte fields in 16-byte CDBs and some questions about the software
write protect bits in mode page 10h.  I'd appreciate feedback from anyone
who can't attend.  We'll discuss your comments in the meeting.

Cheers,

Paul Suhler
Seagate Removable Storage Solutions

-=-=-=-

E/T  Clause  Page  Comment

E   3.1.17 5    Also need to refer to autosense

E   5.3    32   Table 10 Subclause column needs references
                Fix:  Add as needed

T   5.3.1  34   Try to align eight-byte field in ERASE (16) the same as in
other 16-byte commands
                Fix:  Start LOGICAL BLOCK ADDRESS field in byte 3.  Make
byte 11 Reserved.

T   5.3.2  35   Try to align eight-byte field in LOCATE (16) the same as in
other 16-byte commands
                Fix:  Start LOGICAL BLOCK ADDRESS field in byte 3.  Make
byte 11 Reserved.

T   5.4.14 71   Try to align eight-byte field in SPACE (16) the same as in
other 16-byte commands
                Fix:  Start COUNT field in byte 3.  Make byte 11 Reserved.

T   5.5.3.2     88                  Is SWP cleared when medium is unloaded?
Is SWP redundant with ASOCWP?
                Fix:  TBD in working group

E   5.5.3.2     88                  Specify Sense Key for the four WP bit
violations
                Fix:  DATA PROTECT (not WRITE PROTECT)

E   5.5.3.2     88                  Use ASC/ASCQs from SPC-2 for SWP,
ASOCWP, PERSWP, & PERMWP violations
                Fix:  LOGICAL UNIT SOFTWARE WRITE PROTECTED, ASSOCIATED
WRITE PROTECT, PERSISTENT WRITE PROTECT, & PERMANENT WRITE PROTECT,
respectively

T   5.5.3.2     89                  Why does setting SWP, etc. with no
medium report MANUAL INTERVENTION REQUIRED ?
                Fix:  How about LOGICAL UNIT NOT READY, MEDIUM NOT PRESENT
?

E   Tables      Byte-wide fields seem to have names left-justified, rather
than centered.
                Fix:  Center.


T   01-146r0                        E0:E0 Implicit command enabled
                Fix:  Also require ((BOT= False) or (BAML=1)) ?  What
ASC/ASCQ?

T   01-146r0                        F0:E0 Explicit command enabled will end
up in E0 or E1 or E2
                Fix:  Split into three transitions, F0:E0, F0:E1, and F0:E2
?

T   01-146r0                        F0:F0  Implicit tagged command
                Fix:  Need ASC/ASCQs

T   01-146r0                        F0:F0  Explicit untagged command
                Fix:  Need ASC/ASCQs

E   01-146r0                        Two self-loop transitions on E2 are
labeled "E1:E1"
                Fix:  "E2:E2"
-=-=-=-


*
* 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