This message is from the T13 list server.
Robert,
A revision 4 of proposal e02126 will be posted soon that will address the
large physical size issue.
Regards,
Steve Livaccari
Hard Drive Engineering
IBM Global Procurement
Internet: [EMAIL PROTECTED]
Phone (919) 543.7393
"Elliott, Robert
(Server Storage)"
<[EMAIL PROTECTED]> To
Sent by: <[email protected]>
[EMAIL PROTECTED] cc
rg
Subject
[t13] WRITE LONG, SCT Write Long,
06/08/2005 08:11 and WRITE WRONG EXT
PM
ATA offers quite a few ways to perform WRITE LONG and READ LONG
functionality.
1. ATA-3 defined WRITE LONG (command codes 32h and 33h) and READ LONG
(command codes 22h and 23h), including a note that "The committe is
considering removing READ LONG and WRITE LONG commands in a future ATA
standard." The commands are obsolete in ATA-4.
2. The SCT (SMART Command Transport) technical report defines a way to
implement WRITE LONG and READ LONG commands through SMART log pages
(supporting 48-bit LBAs).
Command: SMART READ LOG, SMART WRITE LOG, READ LOG EXT, or WRITE LOG EXT
Log address: E0h (Writes) or E1h (Reads)
SCT Function code: 0001h (Read Long) and 0002h (Write Long)
Those log addresses are marked "Reserved" in ata7v1r4b.
3. Proposal e02126, defining new WRITE WRONG EXT and READ WRONG EXT
commands, has apparently been resurrected.
Any chance of converging on one method? If WRITE WRONG continues, then a
SCSI equivalent would be helpful for the SCSI-to-ATA Translation (SAT)
project.
Since these commands each address a single logical block, it's unclear how
well they will work with long physical sectors, where the ECC bytes are
shared by more than one logical block.
--
Rob Elliott, [EMAIL PROTECTED]
Hewlett-Packard Industry Standard Server Storage Advanced Technology
https://ecardfile.com/id/RobElliott
