From Dave.Landsman at sandisk.com  Fri May  1 07:54:43 2009
From: Dave.Landsman at sandisk.com (Dave Landsman)
Date: Fri, 1 May 2009 17:54:43 +0300
Subject: 09-169r0 Posted: Response to 08-289r1 (Proposal to Revoke
 TrustedFlash Protocol ID)
Message-ID: <mailman.284.1441607349.22516.t10@sandbox.t10.org>

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

T10/09-169r0 (http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-169r0.pdf) has been
uploaded to the T10 site.  This is a response to the proposal to revoke the
TrustedFlash Protocol ID in SPC4.
Dave Landsman
SanDisk Corporation
Standards and Industry Associations
m. 206.484.4782 | t. 206.275.4385


From jgeldman at lexar.com  Fri May  1 11:14:51 2009
From: jgeldman at lexar.com (jgeldman at lexar.com)
Date: Fri, 1 May 2009 11:14:51 -0700
Subject: 09-169r0 Response to 08-289r1 (Proposal to Revoke TrustedFlash Protocol ID)
Message-ID: <mailman.285.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* <jgeldman at lexar.com>
*
It looks like Dave & I will wake people up in CAP.
A line Dave left out from the quoted SD document (numbers removed):
"Security system (xyz) is allocated for the external (third party owned)
security system - TrustedFlash." 
T10, is an INCITs standards committee, authorized by ANSI.  USB, SD, CF,
SATA, etc. are industry consortiums that produce specifications. The
mores are different. 
In the initial approval of the Trusted Flash ID assignment, the initial
request was for a SanDisk reference. That didn't fly with the committee
as we didn't want to "standardize" a vendor proprietary protocol. What
we voted in was conditional on the promise that the technology would be
turned over to an industry consortium. This hasn't occurred since this
all started in 2007.
In the editing process, the protocol reference has turned into a
once-removed vendor proprietary protocol. But it still is vendor
proprietary. This assignment change did not occur in a voted proposal.
This change deserves transparency. This is the issue: Is the lid off for
any proprietary protocol assignment request, or do we keep to the
initial (verbal) guidelines. 
Dave, by the way, thanks for providing examples on the usage of Trusted
Flash. There have been private discussions about taking this into
consideration also.
See you in Seattle,
John Geldman
Director of Industry Standards
Lexar Media
47300 Bayside Parkway
Fremont, CA 94538
P: 510 580-8715
C: 510 449-3597
** Micron/Lexar Confidential **
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From roweber at IEEE.org  Sat May  2 09:42:23 2009
From: roweber at IEEE.org (Ralph Weber)
Date: Sat, 02 May 2009 11:42:23 -0500
Subject: SPC-4 r19 is available
Message-ID: <mailman.286.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* Ralph Weber <roweber at ieee.org>
*
SPC-4 r19 is available from:
http://www.t10.org/cgi-bin/ac.pl?t=f&f=spc4r19.pdf
I gave up on 'normalizing' the log page parameter
definitions as editorial changes. The need to fill
in some many blanks (plus a few cases where what
is already said looks wrong) have obliged me to
handle the task using a TBD document full of
substantive changes.
All the best,
.Ralph
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From lohmeyer at t10.org  Sat May  2 23:00:55 2009
From: lohmeyer at t10.org (T10 Document Administrator)
Date: Sun, 3 May 2009 00:00:55 -0600
Subject: Recent T10 documents uploaded since 2009/04/26
Message-ID: <mailman.287.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* T10 Document Administrator <lohmeyer at t10.org>
*
Proposals
---------
SPC-4: Team Reservation (Proposal)
(by: Kevin Butt)
T10/08-025r4   Uploaded: 2009/04/27   498051 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-025r4.pdf
SMC-3, Report Element Information
(by: Curtis Ballard)
T10/08-066r8   Uploaded: 2009/05/01   139719 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-066r8.pdf
SSC-3: Revision 04a Letter Ballot Comment Database
(by: David Peterson)
T10/08-095r8   Uploaded: 2009/04/30   191779 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-095r8.pdf
SSC-3: Revision 04a Letter Ballot Comment Database
(by: David Peterson)
T10/08-095r8   Uploaded: 2009/04/30   248832 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-095r8.xls
SMC-3 Cleaning error codes
(by: Curtis Ballard)
T10/08-201r3   Uploaded: 2009/04/30   56461 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-201r3.pdf
ADC-3:	I_T Nexus Loss Effect on Bridged Commands
(by: Paul Suhler)
T10/08-301r2   Uploaded: 2009/04/29   17373 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-301r2.pdf
SMC-3 Use of NOT READY error codes
(by: Noud Snelder)
T10/08-320r1   Uploaded: 2009/04/29   30114 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-320r1.pdf
SBC-3: GET LBA STATUS command
(by: Fred Knight, David L. Black)
T10/08-341r1   Uploaded: 2009/04/29   64270 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-341r1.pdf
SPL: Low Power Options for SAS phys
(by: George Penokie)
T10/09-063r2   Uploaded: 2009/04/27   762197 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-063r2.pdf
QSFP+ draft spec proposal
(by: Tom Palkert)
T10/09-084r1   Uploaded: 2009/04/29   436166 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-084r1.pdf
SPC-4/SBC-3/SPL: Power conditions transition modifications
(by: Kevin Marks)
T10/09-085r2   Uploaded: 2009/05/01   140200 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-085r2.pdf
SMC-3 Move volume by indicator
(by: Noud Snelder)
T10/09-086r1   Uploaded: 2009/04/29   72033 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-086r1.pdf
Derivation of SAS-2.1 Active Cable Jitter Spec
(by: Gourgen Oganessyan, Harvey Newman)
T10/09-097r1   Uploaded: 2009/05/01   808695 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-097r1.pdf
SAS 2_1 Active Cable Electrical Characteristics
(by: Gourgen Oganessyan)
T10/09-098r2   Uploaded: 2009/04/30   22190 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-098r2.pdf
SMC-3 TapeAlert Enhancements
(by: Curtis Ballard)
T10/09-109r1   Uploaded: 2009/04/30   131117 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-109r1.pdf
Results of Letter Ballot on recommending approval of SAM-4 FDIS
(by: John Lohmeyer)
T10/09-136r0   Uploaded: 2009/04/30   28061 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-136r0.pdf
Results of Letter Ballot on recommending approval of SAM-4 FDIS
(by: John Lohmeyer)
T10/09-136r0   Uploaded: 2009/04/30   4336 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-136r0.txt
Results of Letter Ballot on forwarding MMC-6 to first public review
(by: John Lohmeyer)
T10/09-138r0   Uploaded: 2009/05/01   45558 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-138r0.pdf
Results of Letter Ballot on forwarding MMC-6 to first public review
(by: John Lohmeyer)
T10/09-138r0   Uploaded: 2009/05/01   11439 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-138r0.txt
SAT-2 Update Translation of ATA errors to SCSI errors for ATA8-ACS
(by: Brad Besmer)
T10/09-147r1   Uploaded: 2009/04/28   13801 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-147r1.pdf
SBC3 - Thin Provisioning unmap per LBA cleanup + TP granularity
(by: Frederick Knight)
T10/09-153r0   Uploaded: 2009/04/27   225597 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-153r0.pdf
Minutes: CAP Thin Provisioning con-call April 22, 2009
(by: Frederick Knight)
T10/09-158r0   Uploaded: 2009/04/27   32778 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-158r0.pdf
SAM5 - CLEAR_ACA status when no ACA condition exists?
(by: Frederick Knight)
T10/09-159r0   Uploaded: 2009/04/27   171659 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-159r0.pdf
SBC-3  Protection Infromation settings during capacity change
(by: George Penokie)
T10/09-160r0   Uploaded: 2009/04/27   79220 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-160r0.pdf
SBC-3  Protection Information settings during capacity change
(by: George Penokie)
T10/09-160r1   Uploaded: 2009/04/28   78406 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-160r1.pdf
SPL: Mislabled wrapping counters in Photocol-Specific Port log page
(by: George Penokie)
T10/09-161r0   Uploaded: 2009/04/28   63348 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-161r0.pdf
SPC-4 Revise LOG SELECT w/ PCR=1 wording
(by: Gerald Houlder)
T10/09-162r0   Uploaded: 2009/04/28   43230 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-162r0.pdf
UAS Letter Ballot Comment Resolutions
(by: Curtis Stevens)
T10/09-163r0   Uploaded: 2009/04/28   765800 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-163r0.fdf
UAS Letter Ballot Comment Resolutions
(by: Curtis Stevens)
T10/09-163r0   Uploaded: 2009/04/28   1707765 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-163r0.pdf
SSC-3: Working Group Agenda, May 5, 2009
(by: David Peterson)
T10/09-164r0   Uploaded: 2009/04/29   11553 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-164r0.pdf
FCP-4: Working Group Agenda, May 5, 2009
(by: David Peterson)
T10/09-165r0   Uploaded: 2009/04/29   9184 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-165r0.pdf
Minutes of SAS PHY Working Group conference call April 23, 2009
(by: Alvin Cox)
T10/09-166r0   Uploaded: 2009/04/29   13543 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-166r0.pdf
SPL - PL_OC2 I_T Nexus loss fixes
(by: George Penokie)
T10/09-167r0   Uploaded: 2009/05/01   166738 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-167r0.pdf
SanDisk response to Lexar proposal to revoke TrustedFlash Protocol ID
in SPC4
(by: Dave Landsman)
T10/09-169r0   Uploaded: 2009/05/01   23539 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-169r0.pdf
Considerations for Common Management Interface for SAS-2.1 Cables
(by: Gourgen Oganessyan)
T10/09-170r0   Uploaded: 2009/04/30   295425 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-170r0.pdf
T11 Liaison Report, April 2009
(by: Claudio DeSanti)
T10/09-177r0   Uploaded: 2009/04/30   11018 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-177r0.pdf
SPC - Add IPv6 target descriptor to XCOPY
(by: Frederick Knight)
T10/09-178r0   Uploaded: 2009/04/30   228620 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-178r0.pdf
SMC-3: Controlling VTL Replication
(by: Roger Cummings)
T10/09-179r0   Uploaded: 2009/05/01   60105 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-179r0.pdf
Working Drafts
--------------
SCSI Primary Commands - 4 (SPC-4)
(Editor: Ralph Weber)
 Rev: 19       Uploaded: 2009/05/02   4855917 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=spc4r19.pdf
SCSI Stream Commands - 3 (SSC-3)
(Editor: Dave Peterson)
 Rev: 04b      Uploaded: 2009/04/30   3129511 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=ssc3r04b.pdf
(Report generated on 2009/05/03 at 00:00:55)
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From MOverby at nvidia.com  Mon May  4 20:30:30 2009
From: MOverby at nvidia.com (Mark Overby)
Date: Mon, 4 May 2009 20:30:30 -0700
Subject: SAT-2 r7 posted
Message-ID: <mailman.288.1441607349.22516.t10@sandbox.t10.org>

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

To try and speed this along, I'm posting r7.
This incorporates all accepted letter ballot comments on the beginning of the
document through the end of clause 5 (excluding comments to Figures 8, 9, and
10 due to visio issues). I would appreciate if you could review you accepted
comments to make sure that they have been incorporated correctly so far.
Document 09-184r0 contains both a PDF and FDF with comment resolution
incorporation. Comments that have been incorporated are marked with the
status "completed" (you can sort on that status).
If you have any questions or comments, feel free to ask.
I appreciate the patience in getting this out.
I expect the next rev to be done towards the end of the week with more of the
comments incorporated. Revisions will step by minor revision as we go along
until I get to the final incorporation. At that point, I will incorporate the
T10 member list and remove the revision history for forwarding and make that
a new major revision number.
-----------------------------------------------------------------------------
------
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.
-----------------------------------------------------------------------------
------


From Bill.Martin at emulex.com  Mon May  4 20:55:18 2009
From: Bill.Martin at emulex.com (Bill.Martin at emulex.com)
Date: Mon, 4 May 2009 20:55:18 -0700
Subject: Another late SAT-2 issue
Message-ID: <mailman.289.1441607349.22516.t10@sandbox.t10.org>

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

In SAT-2 10.2.4.1, the SELF-TEST CODE field value in table 81 is based on the
Self-test descriptor index from the ATA READ LOG EXT command.  This value is
a pointer to the most recent self test descriptor in the Extended Self-test
log data structure (See ACS-2 r1a A.8.2).  SPC-4 requires that the value
returned in the SELF-TEST CODE field shall be the value of the SELF-TEST CODE
field for the most recently executed self test.  The index that is being used
has nothing to do with the SELF-TEST CODE field value for the most recently
executed self test.
To be accurate you would need to look in the self-test descriptor that is
pointed to by the self-test descriptor index and do the reverse translation
of the Content if the LBA field (7:0) of what was done in SAT-2 table 25.  An
alternative would be to put the following requirement in table 81 for the
SELF-TEST CODE field value "set to the SELF-TEST CODE field value of the most
recently executed SEND DIAGNOSTIC command."
Bill Martin
Emulex
Office of Technology
Industry Standards
916 772-3658
916 765-6875 (Cell)
bill.martin at emulex.com


From lohmeyer at t10.org  Tue May  5 11:19:40 2009
From: lohmeyer at t10.org (John Lohmeyer)
Date: Tue, 05 May 2009 12:19:40 -0600
Subject: SAS Protocol WG minutes posted
Message-ID: <mailman.290.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* John Lohmeyer <lohmeyer at t10.org>
*
The SAS Protocol working group minutes of the May 4, 2009 meeting are
available at:
  http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-173r0.htm
--
John Lohmeyer		       Email: lohmeyer at t10.org
LSI Corp.		       Voice: +1-719-533-7560
4420 ArrowsWest Dr.		Cell: +1-719-338-1642
Colo Spgs, CO 80907
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From lohmeyer at t10.org  Tue May  5 12:23:49 2009
From: lohmeyer at t10.org (John Lohmeyer)
Date: Tue, 05 May 2009 13:23:49 -0600
Subject: SAT WG minutes posted
Message-ID: <mailman.291.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* John Lohmeyer <lohmeyer at t10.org>
*
The SAT working group minutes of the May 5, 2009 meeting are available at:
  http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-174r0.htm
--
John Lohmeyer		       Email: lohmeyer at t10.org
LSI Corp.		       Voice: +1-719-533-7560
4420 ArrowsWest Dr.		Cell: +1-719-338-1642
Colo Spgs, CO 80907
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From Alvin.Cox at seagate.com  Tue May  5 18:26:19 2009
From: Alvin.Cox at seagate.com (Alvin.Cox at seagate.com)
Date: Tue, 5 May 2009 20:26:19 -0500
Subject: SAS PHY WG minutes posted
Message-ID: <mailman.292.1441607349.22516.t10@sandbox.t10.org>

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

 http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-188r0.pdf
Alvin Cox
Seagate Technology, LLC
Office 405-392-3738
Cell 405-206-4809


From Alvin.Cox at seagate.com  Tue May  5 18:28:23 2009
From: Alvin.Cox at seagate.com (Alvin.Cox at seagate.com)
Date: Tue, 5 May 2009 20:28:23 -0500
Subject: SAS PHY WG teleconferences
Message-ID: <mailman.293.1441607349.22516.t10@sandbox.t10.org>

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

Bi-weekly teleconferences will be held starting on May 21, 2009.
Call details:
USA Toll Free Dial in Number: (877)810-9442 
International Access/Caller Paid Dial In Number: (636)651-3190 
PARTICIPANT CODE: 3243413 
WEBEX information: 
Topic: SAS-2.1 PHY WG 
Date: Bi-weekly on Thursday, starting 21 May, 2009
Time: 10:00 am, Central Daylight Time 
Meeting Number: 826 515 680 
Meeting Password: newsas 
Alvin Cox
Seagate Technology, LLC
Office 405-392-3738
Cell 405-206-4809


From daviburg at windows.microsoft.com  Wed May  6 07:57:52 2009
From: daviburg at windows.microsoft.com (David Burg)
Date: Wed, 6 May 2009 07:57:52 -0700
Subject: [MtFuji] MMC / Mt Fuji: 8 bytes and 4 bytes flavors of 'No
 Event'
Message-ID: <mailman.294.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* David Burg <daviburg at windows.microsoft.com>
*
Hello,
Regarding the Event Descriptor Length, 0002h and 0006h mismatch this sentence
of the specification:
"The Event Descriptor Length field specifies the number of bytes of data that
follows the Event Status Notification
Header."
The Event Status Notification Header is already 4 bytes long. So that this
specification sentence seems to suggest lengths 0000h and 0004h respectively.
With regards,
David.
-----Original Message-----
From: owner-mtfuji5 at avc-pioneer.com [mailto:owner-mtfuji5 at avc-pioneer.com] On
Behalf Of Takaharu Ai
Sent: Wednesday, April 08, 2009 1:37 AM
To: mtfuji5 at avc-pioneer.com
Cc: T10 Reflector; Ope Aladekomo
Subject: Re: [MtFuji] MMC / Mt Fuji: 8 bytes and 4 bytes flavors of 'No
Event'
Hello David,
[NEA bit]
The definition of this bit in MMC is;
    If NEA (No Event Available) is set to one, the Drive supports none
    of the requested notification classes. If NEA is set to zero, at
    least one of the requested notification classes is supported.
This bit of zero indicates that the drive supports none of the Classes
requested. It is independent from the existence of an occurred Event of
one of the requested Classes.
So, we agree with your following opinion.
> This sounds more like "No Requested Class Supported".
[Response Data length]
Regarding the reported parameter length, our understanding is same as
yours.
If the NEA is set to zero, one Event Descriptor must be transferred
even if no Event has occurred. In this case, the Event Descriptor Length
field is set to 0x0006.
If the NEA is set to one, no Event Descriptor is transferred. In this
case, the Event Descriptor Length field is set to 0x0002.
Best Regards,
Harry Ai
VEBU,
AVC Networks Company,
Panasonic Corporation
Osaka, Japan
---------------- Start of the original message ----------------
>From: David Burg <daviburg at windows.microsoft.com>
>To: "mtfuji5 at avc-pioneer.com" <mtfuji5 at avc-pioneer.com>, T10 Reflector
<t10 at t10.org>
>Cc: Ope Aladekomo <Ope.Aladekomo at microsoft.com>
>Date: Tue, 24 Mar 2009 13:18:01 -0700
>Subject: [MtFuji] MMC / Mt Fuji: 8 bytes and 4 bytes flavors of 'No Event'
>
> Hello,
>
> During our testing of Windows 7, our engineers noticed a difference in the
devices' implementation of GESN command response to say the same 'no event'
answer. Below is a capture of an 8 bytes answer from one device and of an 4
bytes answer from another device.
>
>
> [cid:image001.png at 01C9AC80.A5F1FA20]
>
> (Note that BusTrace incorrectly interpreted the Polled bit as Immed.)
>
> We believe this complies to MMC's:
>
> [cid:image002.jpg at 01C9AC80.A5F1FA20]
>
> (One might want to be careful to clarify "If no event of the requested
notification class has occurred, ..." because event may occur in another
class and yet can't be reported.)
>
> The other device responds:
>
> [cid:image003.png at 01C9AC80.A5F1FA20]
>
> This does not seem allowed by the current spec, although it is not
completely obvious.
>
> Also, some software engineers thought they would get NEA = 1b and 4 bytes,
based on the name of that bit "Not Event Available". From an English language
point of view, there is indeed no event available. However, the spec
definition of the bit then contradicts with what one would expect out of
English language alone:
>
> "If NEA (No Event Available) is set to one, the Drive supports none of the
requested notification classes. If NEA
> is set to zero, at least one of the requested notification classes is
supported."
>
> This sounds more like "No Requested Class Supported".
>
> So, Microsoft believes this GESN section should be reviewed in detail and
clarified.
>
> With regards,
>
> David.
>
----------------- End of the original message -----------------
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From curtis.ballard at hp.com  Thu May  7 10:30:42 2009
From: curtis.ballard at hp.com (Ballard, Curtis C (StorageWorks))
Date: Thu, 7 May 2009 17:30:42 +0000
Subject: SMC-3 teleconference 13 May, 2009 8-10 AM PDT
Message-ID: <mailman.295.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* "Ballard, Curtis C (StorageWorks)" <curtis.ballard at hp.com>
*
The SMC-3 working group will host a teleconference on Wednesday 13, May 2009
beginning at 8:00 AM PDT and concluding at 10:00 AM PDT.  The conference call
will be hosted by SYMANTEC and connection details follow.  For non-US dial in
numbers see the complete bridge number list following the agenda.
The agenda will follow the conference call details.
Conference bridge
All numbers provided by SYMANTEC.
US Dial In Numbers
Dial-In Numbers:    1-877-860-3058 (toll-free within the US & Canada)
		    or	1-719-867-1571 (caller paid)
Participant Passcode: 3730724975
WEB MEETING
http://webmeeting.dimdim.com/portal/JoinForm.action?confKey=rogerjc&asPresent
er=false&meetingId=da50f29c-65e9-4f52-8941-b81926b531aa&attendeePwd=5698
In advance of the call, please check that your system has all the
prerequisites by going to:
http://www.dimdim.com/support/dimdim_tools.html
DimDim allows PDFs and PPTs to be shared as documents. If you need to display
another type of file, the way to do that is to share your desktop. To do that
before the call please download the plugin at:
http://webmeeting.dimdim.com/dimdim/html/envcheck/publisherinstall.action
Draft Agenda -- SCSI Media Changer (SMC) Working Group Meeting
    Location -- Ad Hoc Teleconference
	Date -- 13 May, 2009
	Time -- 8:00 AM PDT
1	Opening remarks and introductions
1.1	Antitrust Guidelines and INCITS Patent Policy 
	(http://www.incits.org/pat_slides.pdf)
1.2	Meeting Documents
1.3	Introductions
2	Approval of the Agenda
3	Attendance and Membership
4	Approval of previous meeting minutes (09-156)
5	Review of action items
6	Old Business
6.1	Working List for ISV feedback (SMC/SSC/ADC/SPC) (07-131) [Butt]
6.2	SMC-3 TapeAlert Enhancements (09-109) [Ballard]
6.3	SMC-3 Report Volume Information (08-215) [Ballard]
6.4	SMC-3 Report Element Information (08-066) [Ballard]
6.5	SMC-3 Use of LOGICAL UNIT NOT READY, OFFLINE (08-260) [Snelder]
6.6	SMC-3 New additional sense codes tracking document (08-272) [Wideman]
6.7	SMC-3 Use of NOT READY error codes (08-320) [Snelder]
6.8	SMC-3 Use of element descriptor sense codes (08-432) [Snelder] 
6.9	SMC-3 Move volume by indicator (09-086) [Snelder]
6.10	SMC-3: Controlling VTL Replication (09-179) [Cummings]
6.11	SMC-3 Updated to reference SPC-4
7	New Business
8	Plans for SMC-3 call for final technical input
9	Next Meeting Requirements 
10	Review New Action Items 
11	Adjournment
International Access Numbers
Local (Australia, Sydney): +61 (0) 2 8207 3476
Local (Austria, Vienna): +43 (0) 1 274 872 5014
Local (Belgium, Brussels): +32 (0) 2 300 1141
Local (Brazil, Sao Paolo): +55 11 5582 6540
Local (Denmark, Copenhagen): +45 70 14 49 51
Local (France, Paris): +33 (0) 1 72 69 79 21
Local (Germany, Frankfurt): +49 (0) 69 12009 821
Local (Hong Kong): +852 3008 0319
Local (Ireland, Dublin): +353 (0) 1 437 0812
Local (Italy, Milan): +39 02 897 819 49
Local (Italy, Turin): +39 01 121 792 102
Local (Japan, Tokyo): +81 (0) 3 4455 1490
Local (Netherlands, Amsterdam): +31 (0) 20 262 9506
Local (Singapore): +65 6517 0626
Local (Spain, Barcelona): +34 93 802 0290
Local (Spain, Madrid): +34 91 829 8567
Local (Spain, Valencia): +34 96 314 6021
Local (Sweden, Stockholm): +46 (0) 8 5205 4923
Local (Switzerland, Geneva): +41 (0) 22 555 0202
Local (Switzerland, Zurich): +41 (0 ) 44 556 8414
Local (UK, London): +44 (0) 20 7078 9142
International toll free (Argentina): 0800 666 0109
International toll free (Australia): 1 800 223 765
International toll free (Austria): 0800 293 774
International toll free (Belgium): 0 800 71 003
International toll free (Chile): 123 0020 9174
International toll free (China, Northern Region): 10 800 714 1252
International toll free (China, Southern Region): 10 800 140 1248
International toll free (Colombia): 01 800 518 0911
International toll free (Czech Republic): 800 700 454
International toll free (Denmark): 80 889 437
International toll free (Dominican Republic): 1 888 751 4508
International toll free (Ecuador): 1 800 020 308
International toll free (France): 0 800 911 063
International toll free (Germany): 0 800 180 9082
International toll free (Greece): 00 800 161 2205 7120
International toll free (Hong Kong): 800 965 260
International toll free (Hungary): 06 800 165 79
International toll free (India): 000 800 1007 180
International toll free (Indonesia): 001 803 017 7120
International toll free (Ireland): 1 800 949 010
International toll free (Israel): 1 80 924 6088
International toll free (Italy): 800 871 337
International toll free (Japan): 00531 16 0910
International toll free (Latvia): 800 2861
International toll free (Lithuania): 8 800 3 06 61
International toll free (Luxembourg): 800 2 5702
International toll free (Malaysia): 1 800 814 070
International toll free (Mexico): 001 800 514 7120
International toll free (Monaco): 800 93 479
International toll free (Netherlands): 0 800 024 9671
International toll free (New Zealand): 0 800 451 385
International toll free (Norway): 800 109 47
International toll free (Panama): 00 800 226 6884
International toll free (Poland): 00 800 112 40 37
International toll free (Portugal): 800 819 891
International toll free (Russia): 810 800 2781 1012
International toll free (Singapore): 800 101 2103
International toll free (Slovenia): 0 800 80276
International toll free (South Africa): 0 800 981 390
International toll free (South Korea): 003 0813 2115
International toll free (Spain): 900 947 686
International toll free (Sweden): 02 079 7945
International toll free (Switzerland): 0 800 896 483
International toll free (Thailand): 001 800 156 205 7120
International toll free (Trinidad-Tobago): 1 800 205 7120
International toll free (UK): 0 808 101 1558
International toll free (Uruguay): 0004 019 0254
International toll free (Venezuela): 0 800 100 8414
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From MOverby at nvidia.com  Thu May  7 14:00:09 2009
From: MOverby at nvidia.com (Mark Overby)
Date: Thu, 7 May 2009 14:00:09 -0700
Subject: SAT-2 r7a posted
Message-ID: <mailman.296.1441607349.22516.t10@sandbox.t10.org>

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

r7a incorporates changes up through (and including) clause 6 (sans Visio
diagram updates due to an incompatibility with XP SP3 and Frame and Visio
together).
The FDF is also posted for review. Completed comments indicate that they have
been incorporated.
Comments welcome.
Expect further revisions in the next few days.
There will be a clean version (r8) when all comments have been incorporated
and all necessary items incorporated.
-----------------------------------------------------------------------------
------
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.
-----------------------------------------------------------------------------
------


From curtis.stevens at wdc.com  Thu May  7 14:06:09 2009
From: curtis.stevens at wdc.com (Curtis Stevens)
Date: Thu, 7 May 2009 14:06:09 -0700
Subject: UAS Comment Resolution Telecon
Message-ID: <mailman.297.1441607349.22516.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r0905072_f.htm">HTML-formatted message</a>
Attachment #1: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r0905072_meeting.ics">meeting.ics</a>

When: Wednesday, May 27, 2009 9:00 AM-1:00 PM (GMT-08:00) Pacific Time (US &
Canada).
Where: WebEx
*~*~*~*~*~*~*~*~*~*
Proposed Agenda:
1.	Introductions at 9:00am PT
2.	Letter Ballot comment resolution
3.	Other items as time permits
4.	Adjourn by 1pm
The WebEx will be up at 8:45am PT.  Please call in early so the meeting can
start on time.
*** Please start the WebEx before calling the conference bridge.  If you
call into the conference bridge, please include the attendee number provided
by the WebEx client. ***
If you have questions about this conference, please E-Mail Curtis Stevens
Curtis.Stevens at wdc.com or call at 949-672-7933
Curtis Stevens invites you to an online meeting using WebEx.
Meeting Number: 571 276 475
Meeting Password: UA5Telecon
-------------------------------------------------------
To join this meeting
-------------------------------------------------------
1. Go to https://wdc007.webex.com/wdc007/j.php?J=571276475
2. Enter the meeting password: UA5Telecon
3. Click "Join Now".
4. Follow the instructions that appear on your screen.
-------------------------------------------------------
Audio conference information
-------------------------------------------------------
Call-in toll number (US/Canada): 1-408-792-6300
Access code:571 276 475
http://www.webex.com
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio
and any documents and other materials exchanged or viewed during the session
to be recorded. By joining this session, you automatically consent to such
recordings. If you do not consent to the recording, do not join the session.


From billpp at gmail.com  Fri May  8 08:52:28 2009
From: billpp at gmail.com (Flavio Junior)
Date: Fri, 8 May 2009 12:52:28 -0300
Subject: WRITE_AND_VERIFY doubt
Message-ID: <mailman.298.1441607349.22516.t10@sandbox.t10.org>

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

Hi folks, afternoon.
I've a tad doubt when writing a simple code to sends a WRITE_AND_VERIFY
(0x2E) command to a scsi device.
I need to do it to decide if this is a primary (and read-write) storage or a
secundary (and read-only) storage (ibm ds4700), and adjust my I/O MultiPath
priority accordingly, and i need to run it periodically to check if the
roles change.
My doubt is, is there a area that I cant safety use this command without
risk to corrupt the data on disk? I'm not a really developer, just make some
researches and read some codes to assembly my own, here is the code:
http://pastebin.com/m22b06f04
O course, if there is a way more elegant to get this info I'll appreciate if
someone says me. :)
Really thanks in advance and some sorries for english and dumb question.
--
Fl?vio do Carmo J?nior
Florianopolis/SC, Brazil


From konrad at virtualiron.com  Fri May  8 09:50:11 2009
From: konrad at virtualiron.com (Konrad Rzeszutek)
Date: Fri, 8 May 2009 12:50:11 -0400
Subject: WRITE_AND_VERIFY doubt
Message-ID: <mailman.299.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* Konrad Rzeszutek <konrad at virtualiron.com>
*
On Fri, May 08, 2009 at 12:52:28PM -0300, Flavio Junior wrote:
> Hi folks, afternoon.
> 
> I've a tad doubt when writing a simple code to sends a WRITE_AND_VERIFY
> (0x2E) command to a scsi device.
> 
> I need to do it to decide if this is a primary (and read-write) storage or
a
> secundary (and read-only) storage (ibm ds4700), and adjust my I/O MultiPath
I was under the impression that the DS4700 was an RDAC device. Meaning
you can use these settings:
 device {
	vendor		"IBM"
	product 	"1814"
	hardware_handler    "1 rdac"
	path_grouping_policy	group_by_prio
	prio		"rdac"
	failback	immediate
	path_checker	    rdac
    }
And it will detect whether your secondary paths are not in usage and
call them 'ghost'.
> priority accordingly, and i need to run it periodically to check if the
> roles change.
> 
> My doubt is, is there a area that I cant safety use this command without
> risk to corrupt the data on disk? I'm not a really developer, just make
some
You will cause corruption.
> researches and read some codes to assembly my own, here is the code:
> http://pastebin.com/m22b06f04
> 
> 
> O course, if there is a way more elegant to get this info I'll appreciate
if
> someone says me. :)
I think using the right multipath.conf entry should do it.
> 
> 
> Really thanks in advance and some sorries for english and dumb question.
> 
> 
> --
> 
> Fl?vio do Carmo J?nior
> Florianopolis/SC, Brazil
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From daviburg at windows.microsoft.com  Fri May  8 10:06:45 2009
From: daviburg at windows.microsoft.com (David Burg)
Date: Fri, 8 May 2009 10:06:45 -0700
Subject: MMC/Mt Fuji: Clarification of AN host implementation from Mt Fuji
 meeting minutes
Message-ID: <mailman.300.1441607349.22516.t10@sandbox.t10.org>

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

Hello,
I noticed in the Fuji meeting minutes from April the following statement:
"1. Test Unit Ready polling also is stopped. Then host software cannot obtain
open/close condition of tray/drawer from OS."
This filtering of Test Unit Ready is only a mistake of an early Windows 7
implementation based on the original SATA AN link behavior specification
before the Mt Fuji specification of the device behavior. This mistake has
since be corrected. Please use the new Windows 7 RC build for your testing.
Test Unit Ready is not filtered any longer.
With regards,
David.


From billpp at gmail.com  Fri May  8 11:33:39 2009
From: billpp at gmail.com (Flavio Junior)
Date: Fri, 8 May 2009 15:33:39 -0300
Subject: WRITE_AND_VERIFY doubt
Message-ID: <mailman.301.1441607349.22516.t10@sandbox.t10.org>

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

Very interesting points Frederick, really thanks..
I'd tried the read-only bit before, seems don't work, but i'll do it again
with more attention. And others ideas should work. Thanks again :).
I'll post results here.
--
Fl?vio do Carmo J?nior
Florianopolis/SC, Brazil
On Fri, May 8, 2009 at 1:40 PM, Knight, Frederick <
Frederick.Knight at netapp.com> wrote:
>  Why don't you just look at the read only bit?  Does the IBM ds4700 not
> report the read only bit for a read only device?  It's the WP bit in the
> mode page header.  Just use MODE SENSE on your favorite mode page to check
> it.
>
> And no, there isn't any "reserved" space you can write to and be safe.
> Another choice would be ORWRITE (and don't "or" in any bits), or XDWRITE
> (and don't "xor" in any bits).  These would all be ways to "write" without
> changing the data in the LBA (although it is possible the device could
> optimize the write step into nothingness).
>
>     Fred Knight
>
>  ------------------------------
> *From:* Flavio Junior [mailto:billpp at gmail.com]
> *Sent:* Friday, May 08, 2009 11:52 AM
> *To:* t10 at t10.org
> *Subject:* WRITE_AND_VERIFY doubt
>
> Hi folks, afternoon.
>
> I've a tad doubt when writing a simple code to sends a WRITE_AND_VERIFY
> (0x2E) command to a scsi device.
>
> I need to do it to decide if this is a primary (and read-write) storage or
> a secundary (and read-only) storage (ibm ds4700), and adjust my I/O
> MultiPath priority accordingly, and i need to run it periodically to check
> if the roles change.
>
> My doubt is, is there a area that I cant safety use this command without
> risk to corrupt the data on disk? I'm not a really developer, just make
some
> researches and read some codes to assembly my own, here is the code:
> http://pastebin.com/m22b06f04
>
>
> O course, if there is a way more elegant to get this info I'll appreciate
> if someone says me. :)
>
>
> Really thanks in advance and some sorries for english and dumb question.
>
>
> --
>
> Fl?vio do Carmo J?nior
> Florianopolis/SC, Brazil
>


From billpp at gmail.com  Fri May  8 11:41:56 2009
From: billpp at gmail.com (Flavio Junior)
Date: Fri, 8 May 2009 15:41:56 -0300
Subject: WRITE_AND_VERIFY doubt
Message-ID: <mailman.302.1441607349.22516.t10@sandbox.t10.org>

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

Hi Konrad, thanks for your answer, but...
I've already configured multipath to group my 4 paths to same LUN as a
single device, the problem here is about 2 different LUN's.
These LUN's are different because it comes from distinct storages devices, I
want to group both because the contents is being replicated by DS4700
Enhanced Remote Mirror feature.
--
Fl?vio do Carmo J?nior
Florian?polis/SC, Brazil
On Fri, May 8, 2009 at 1:50 PM, Konrad Rzeszutek
<konrad at virtualiron.com>wrote:
> On Fri, May 08, 2009 at 12:52:28PM -0300, Flavio Junior wrote:
> > Hi folks, afternoon.
> >
> > I've a tad doubt when writing a simple code to sends a WRITE_AND_VERIFY
> > (0x2E) command to a scsi device.
> >
> > I need to do it to decide if this is a primary (and read-write) storage
> or a
> > secundary (and read-only) storage (ibm ds4700), and adjust my I/O
> MultiPath
>
> I was under the impression that the DS4700 was an RDAC device. Meaning
> you can use these settings:
>
>  device {
>	 vendor 	 "IBM"
>	 product	 "1814"
>	 hardware_handler    "1 rdac"
>	 path_grouping_policy	 group_by_prio
>	 prio		 "rdac"
>	 failback	 immediate
>	 path_checker	     rdac
>    }
>
>
> And it will detect whether your secondary paths are not in usage and
> call them 'ghost'.
>
> > priority accordingly, and i need to run it periodically to check if the
> > roles change.
> >
> > My doubt is, is there a area that I cant safety use this command without
> > risk to corrupt the data on disk? I'm not a really developer, just make
> some
>
> You will cause corruption.
> > researches and read some codes to assembly my own, here is the code:
> > http://pastebin.com/m22b06f04
> >
> >
> > O course, if there is a way more elegant to get this info I'll appreciate
> if
> > someone says me. :)
>
> I think using the right multipath.conf entry should do it.
> >
> >
> > Really thanks in advance and some sorries for english and dumb question.
> >
> >
> > --
> >
> > Fl?vio do Carmo J?nior
> > Florianopolis/SC, Brazil
>


From lohmeyer at t10.org  Fri May  8 11:56:36 2009
From: lohmeyer at t10.org (John Lohmeyer)
Date: Fri, 08 May 2009 12:56:36 -0600
Subject: CAP minutes posted
Message-ID: <mailman.303.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* John Lohmeyer <lohmeyer at t10.org>
*
The draft CAP working group minutes of the May 5-7, 2009 meeting are
available at:
  http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-175r0.htm
--
John Lohmeyer		       Email: lohmeyer at t10.org
LSI Corp.		       Voice: +1-719-533-7560
4420 ArrowsWest Dr.		Cell: +1-719-338-1642
Colo Spgs, CO 80907
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From Yanling.Qi at lsi.com  Fri May  8 14:05:03 2009
From: Yanling.Qi at lsi.com (Qi, Yanling)
Date: Fri, 8 May 2009 15:05:03 -0600
Subject: WRITE_AND_VERIFY doubt
Message-ID: <mailman.304.1441607349.22516.t10@sandbox.t10.org>

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

Flavio,
I think I understand your configuration. You have two DS4700 arrays. You
replicate your volumes between the two arrays. Both the primary volumes and
the secondary (the replicated) volumes are visible to your Linux host. The
replicated volume has write-protection. If the Linux host can not access the
primary volumes or a primary volume becomes secondary (due to role switch),
you would like to start your read/write access to your new primary volume.
First, the device-mapper multupathing is not designed for "storage array
failover". The array failover could be handled in the level higher than the
DM-MP or the application level.  Secondly, the replication, most of times, is
for disaster recovery between two sites. I would be interested in your use
case why you would like to have array failover on the same Linux host.
Thanks,
Yanling
________________________________
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Flavio Junior
Sent: Friday, May 08, 2009 1:42 PM
To: t10 at t10.org
Subject: Re: WRITE_AND_VERIFY doubt
Hi Konrad, thanks for your answer, but...
I've already configured multipath to group my 4 paths to same LUN as a single
device, the problem here is about 2 different LUN's.
These LUN's are different because it comes from distinct storages devices, I
want to group both because the contents is being replicated by DS4700
Enhanced Remote Mirror feature.
--
Fl?vio do Carmo J?nior
Florian?polis/SC, Brazil
On Fri, May 8, 2009 at 1:50 PM, Konrad Rzeszutek
<konrad at virtualiron.com> wrote:
On Fri, May 08, 2009 at 12:52:28PM -0300, Flavio Junior wrote:
> Hi folks, afternoon.
>
> I've a tad doubt when writing a simple code to sends a WRITE_AND_VERIFY
> (0x2E) command to a scsi device.
>
> I need to do it to decide if this is a primary (and read-write) storage or
a
> secundary (and read-only) storage (ibm ds4700), and adjust my I/O MultiPath
I was under the impression that the DS4700 was an RDAC device. Meaning
you can use these settings:
 device {
       vendor	       "IBM"
       product	       "1814"
       hardware_handler    "1 rdac"
       path_grouping_policy    group_by_prio
       prio	       "rdac"
       failback        immediate
       path_checker	   rdac
   }
And it will detect whether your secondary paths are not in usage and
call them 'ghost'.
> priority accordingly, and i need to run it periodically to check if the
> roles change.
>
> My doubt is, is there a area that I cant safety use this command without
> risk to corrupt the data on disk? I'm not a really developer, just make
some
You will cause corruption.
> researches and read some codes to assembly my own, here is the code:
> http://pastebin.com/m22b06f04
>
>
> O course, if there is a way more elegant to get this info I'll appreciate
if
> someone says me. :)
I think using the right multipath.conf entry should do it.
>
>
> Really thanks in advance and some sorries for english and dumb question.
>
>
> --
>
> Fl?vio do Carmo J?nior
> Florianopolis/SC, Brazil


From billpp at gmail.com  Fri May  8 15:48:18 2009
From: billpp at gmail.com (Flavio Junior)
Date: Fri, 8 May 2009 19:48:18 -0300
Subject: WRITE_AND_VERIFY doubt
Message-ID: <mailman.305.1441607349.22516.t10@sandbox.t10.org>

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

On Fri, May 8, 2009 at 6:05 PM, Qi, Yanling <Yanling.Qi at lsi.com> wrote:
>  Flavio,
>
>
>
> I think I understand your configuration. You have two DS4700 arrays. You
> replicate your volumes between the two arrays. Both the primary volumes and
> the secondary (the replicated) volumes are visible to your Linux host. The
> replicated volume has write-protection. If the Linux host can not access
the
> primary volumes or a primary volume becomes secondary (due to role switch),
> you would like to start your read/write access to your new primary volume.
>
Yes Yanling, this is exactly what I have. Under dm-multipath i've eugenio
LSI RDAC (MPP) driver doing its work for multipath to same LUN's/devices.
Something like:
primary storage LU (path1, path2, path3, path4) -> eugenio RDAC driver
path1+path2+path3+path4 = /dev/sdb
secundary storage LU (path1, path2, path3, path4) -> eugenio RDAC driver
path1+path2+path3+path4 = /dev/sdf
/dev/sdb + /dev/sdf -> dm-multipath -> /dev/mpath/alias0
and "alias0" is my device to work to.
>
>
> First, the device-mapper multupathing is not designed for ?storage array
> failover?. The array failover could be handled in the level higher than the
> DM-MP or the application level.  Secondly, the replication, most of times,
> is for disaster recovery between two sites. I would be interested in your
> use case why you would like to have array failover on the same Linux host.
>
Well, I've four nodes on cluster accessing the primary storage device, 2
nodes on build-1 and 2 nodes on build-2.
Something like below square at this image:
http://img139.imageshack.us/img139/642/clusters.jpg
If I can configure DM-MP to handle those two paths, in case of a "disaster"
(or even a storage failure, burning, crash...) i can easily promote the
another one to primary and all my systems (mainly use of cluster is a
file-server) becomes online again. I've no much to concern about data as
this is a sync replication (worst case if i got a filesystem/data corrupt).
Please, excuse me if i'm doing something nasty. This is my first work with
that kind of hardware and I have no friends to ask to.
And if you have any tips, hints, comments, recommendations for me, i'll be
really grateful :).
>
>
> Thanks,
>
> Yanling
>
>
>
Thank you,
--
Fl?vio do Carmo J?nior
Florianopolis/SC, Brasil
>   ------------------------------
>
> *From:* owner-t10 at t10.org [mailto:owner-t10 at t10.org] *On Behalf Of *Flavio
> Junior
> *Sent:* Friday, May 08, 2009 1:42 PM
> *To:* t10 at t10.org
> *Subject:* Re: WRITE_AND_VERIFY doubt
>
>
>
> Hi Konrad, thanks for your answer, but...
>
> I've already configured multipath to group my 4 paths to same LUN as a
> single device, the problem here is about 2 different LUN's.
> These LUN's are different because it comes from distinct storages devices,
> I want to group both because the contents is being replicated by DS4700
> Enhanced Remote Mirror feature.
>
> --
>
> Fl?vio do Carmo J?nior
> Florian?polis/SC, Brazil
>
> On Fri, May 8, 2009 at 1:50 PM, Konrad Rzeszutek <konrad at virtualiron.com>
> wrote:
>
> On Fri, May 08, 2009 at 12:52:28PM -0300, Flavio Junior wrote:
> > Hi folks, afternoon.
> >
> > I've a tad doubt when writing a simple code to sends a WRITE_AND_VERIFY
> > (0x2E) command to a scsi device.
> >
> > I need to do it to decide if this is a primary (and read-write) storage
> or a
> > secundary (and read-only) storage (ibm ds4700), and adjust my I/O
> MultiPath
>
> I was under the impression that the DS4700 was an RDAC device. Meaning
> you can use these settings:
>
>  device {
>	 vendor 	 "IBM"
>	 product	 "1814"
>	 hardware_handler    "1 rdac"
>	 path_grouping_policy	 group_by_prio
>	 prio		 "rdac"
>	 failback	 immediate
>	 path_checker	     rdac
>    }
>
>
> And it will detect whether your secondary paths are not in usage and
> call them 'ghost'.
>
>
> > priority accordingly, and i need to run it periodically to check if the
> > roles change.
> >
> > My doubt is, is there a area that I cant safety use this command without
> > risk to corrupt the data on disk? I'm not a really developer, just make
> some
>
> You will cause corruption.
>
> > researches and read some codes to assembly my own, here is the code:
> > http://pastebin.com/m22b06f04
> >
> >
> > O course, if there is a way more elegant to get this info I'll appreciate
> if
> > someone says me. :)
>
> I think using the right multipath.conf entry should do it.
>
> >
> >
> > Really thanks in advance and some sorries for english and dumb question.
> >
> >
> > --
> >
> > Fl?vio do Carmo J?nior
> > Florianopolis/SC, Brazil
>
>
>


From billpp at gmail.com  Fri May  8 15:59:12 2009
From: billpp at gmail.com (Flavio Junior)
Date: Fri, 8 May 2009 19:59:12 -0300
Subject: WRITE_AND_VERIFY doubt
Message-ID: <mailman.306.1441607349.22516.t10@sandbox.t10.org>

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

On Fri, May 8, 2009 at 1:40 PM, Knight, Frederick <
Frederick.Knight at netapp.com> wrote:
>  Why don't you just look at the read only bit?  Does the IBM ds4700 not
> report the read only bit for a read only device?  It's the WP bit in the
> mode page header.  Just use MODE SENSE on your favorite mode page to check
> it.
>
Yes Frederick, this seems to work, at least with some good code, as
sg3_utils can show:
* Querying to a secundary device:
[root at cerebro src]# sg_modes /dev/sdb
    IBM       VirtualDisk	0916   peripheral_type: disk [0x0]
mode sense (10):  Fixed format, current;  Sense key: Data Protect
 Additional sense: Write protected
[root at cerebro src]# echo $?
99
* Querying to a primary device:
[root at cerebro src]# sg_modes /dev/sdf
    IBM       VirtualDisk	0916   peripheral_type: disk [0x0]
Mode parameter header from MODE SENSE(10):
  Mode data length=242, medium type=0x00, WP=0, DpoFua=1, longlba=0
  Block descriptor length=8
> Direct access device block descriptors:
   Density code=0x0
 00	00 00 00 00 00 00 02 00
[root at cerebro src]# echo $?
0
The problem now is write something to handle with mode page. I'm looking at
sg3_modes.c code but this is a bit complex to me.
Does you have something more easy/clear to help me? The
"SCSI-Programming-HOWTO" is not helping so much.
Thanks again.
--
Fl?vio do Carmo J?nior
Florianopolis/SC, Brasil
>
> And no, there isn't any "reserved" space you can write to and be safe.
> Another choice would be ORWRITE (and don't "or" in any bits), or XDWRITE
> (and don't "xor" in any bits).  These would all be ways to "write" without
> changing the data in the LBA (although it is possible the device could
> optimize the write step into nothingness).
>
>     Fred Knight
>
>  ------------------------------
> *From:* Flavio Junior [mailto:billpp at gmail.com]
> *Sent:* Friday, May 08, 2009 11:52 AM
> *To:* t10 at t10.org
> *Subject:* WRITE_AND_VERIFY doubt
>
> Hi folks, afternoon.
>
> I've a tad doubt when writing a simple code to sends a WRITE_AND_VERIFY
> (0x2E) command to a scsi device.
>
> I need to do it to decide if this is a primary (and read-write) storage or
> a secundary (and read-only) storage (ibm ds4700), and adjust my I/O
> MultiPath priority accordingly, and i need to run it periodically to check
> if the roles change.
>
> My doubt is, is there a area that I cant safety use this command without
> risk to corrupt the data on disk? I'm not a really developer, just make
some
> researches and read some codes to assembly my own, here is the code:
> http://pastebin.com/m22b06f04
>
>
> O course, if there is a way more elegant to get this info I'll appreciate
> if someone says me. :)
>
>
> Really thanks in advance and some sorries for english and dumb question.
>
>
> --
>
> Fl?vio do Carmo J?nior
> Florianopolis/SC, Brazil
>


From lohmeyer at t10.org  Sat May  9 23:00:50 2009
From: lohmeyer at t10.org (T10 Document Administrator)
Date: Sun, 10 May 2009 00:00:50 -0600
Subject: Recent T10 documents uploaded since 2009/05/03
Message-ID: <mailman.307.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* T10 Document Administrator <lohmeyer at t10.org>
*
Proposals
---------
SAT-3: NV Cache Translation
(by: Mark Overby)
T10/08-018r5   Uploaded: 2009/05/06   115423 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-018r5.pdf
SMC-3 Report Volume Information
(by: Curtis Ballard)
T10/08-215r5   Uploaded: 2009/05/03   134582 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-215r5.pdf
ADC-3: Remove Configure Encryption Policy mounted volume restriction
(by: Rod Wideman)
T10/08-247r3   Uploaded: 2009/05/04   19478 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-247r3.pdf
SMC-3, Use of LOGICAL UNIT NOT READY, OFFLINE
(by: Noud Snelder)
T10/08-260r1   Uploaded: 2009/05/06   27954 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-260r1.pdf
ADC-3:	I_T Nexus Loss Effect on Bridged Commands
(by: Paul Suhler)
T10/08-301r3   Uploaded: 2009/05/04   17213 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-301r3.pdf
SMC-3 Use of NOT READY error codes
(by: Noud Snelder)
T10/08-320r2   Uploaded: 2009/05/06   31512 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-320r2.pdf
SBC-3: GET LBA STATUS command
(by: David L. Black)
T10/08-341r2   Uploaded: 2009/05/06   61696 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-341r2.pdf
SPC-4: Device constituent VPD page
(by: Kevin Butt)
T10/09-033r4   Uploaded: 2009/05/06   92197 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-033r4.pdf
SBC-3, More background scan clean-up
(by: Mark Evans)
T10/09-038r2   Uploaded: 2009/05/05   88510 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-038r2.pdf
SBC-3, More background scan clean-up
(by: Mark Evans)
T10/09-038r3   Uploaded: 2009/05/06   89942 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-038r3.pdf
T13 Liaison Report May 09
(by: Dan Colegrove)
T10/09-055r2   Uploaded: 2009/05/07   9842 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-055r2.pdf
QSFP+ draft spec proposal
(by: Tom Palkert)
T10/09-084r2   Uploaded: 2009/05/05   385244 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-084r2.pdf
QSFP+ draft spec proposal
(by: Tom Palkert)
T10/09-084r3   Uploaded: 2009/05/07   165572 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-084r3.pdf
SMC-3 Move volume by indicator
(by: Noud Snelder)
T10/09-086r2   Uploaded: 2009/05/06   80366 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-086r2.pdf
SPC-4, Rectifying conflicts for DEVOFFL and UNITOFFL
(by: Mark Evans)
T10/09-087r2   Uploaded: 2009/05/06   20106 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-087r2.pdf
SBC-3 Allow vendor specific log parameters in log page 15h
(by: Gerald Houlder)
T10/09-088r1   Uploaded: 2009/05/07   41184 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-088r1.pdf
Derivation of SAS-2.1 Active Cable Jitter Spec
(by: Gourgen Oganessyan, Harvey Newman)
T10/09-097r2   Uploaded: 2009/05/04   760548 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-097r2.pdf
Derivation of SAS-2.1 Active Cable Jitter Spec
(by: Gourgen Oganessyan, Harvey Newman)
T10/09-097r3   Uploaded: 2009/05/05   990730 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-097r3.pdf
SAS 2_1 Active Cable Electrical Characteristics
(by: Gourgen Oganessyan)
T10/09-098r3   Uploaded: 2009/05/04   22413 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-098r3.pdf
SAS 2_1 Active Cable Electrical Characteristics
(by: Gourgen Oganessyan)
T10/09-098r4   Uploaded: 2009/05/05   28930 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-098r4.pdf
SAS 2_1 Active Cable Electrical Characteristics
(by: Gourgen Oganessyan)
T10/09-098r5   Uploaded: 2009/05/05   21096 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-098r5.pdf
SAT-2 Standby translation modifications
(by: William Martin)
T10/09-113r3   Uploaded: 2009/05/06   114606 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-113r3.pdf
SBC3 - Thin Provisioning unmap per LBA cleanup + TP granularity
(by: Frederick Knight)
T10/09-153r1   Uploaded: 2009/05/06   229796 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-153r1.pdf
Minutes SSC-3 Working Group May 05, 2009
(by: Kevin Butt)
T10/09-155r0   Uploaded: 2009/05/07   59389 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-155r0.pdf
SAM5 - CLEAR_ACA status when no ACA condition exists?
(by: Frederick Knight)
T10/09-159r1   Uploaded: 2009/05/06   172112 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-159r1.pdf
ADI-2 Working Group Report to Plenary, May 2009
(by: Paul Suhler)
T10/09-168r0   Uploaded: 2009/05/04   73379 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-168r0.pdf
SMC-3 Plenary Report for May 4 2009
(by: Curtis Ballard)
T10/09-171r0   Uploaded: 2009/05/07   11224 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-171r0.pdf
Minutes of SAS Protocol Working Group - May 4, 2009
(by: Weber & Lohmeyer)
T10/09-173r0   Uploaded: 2009/05/05   33657 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-173r0.htm
Minutes of SAS Protocol Working Group - May 4, 2009
(by: Weber & Lohmeyer)
T10/09-173r0   Uploaded: 2009/05/05   98169 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-173r0.pdf
Minutes of SAT Working Group - May 5, 2009
(by: Lohmeyer & Overby)
T10/09-174r0   Uploaded: 2009/05/05   33287 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-174r0.htm
Minutes of SAT Working Group - May 5, 2009
(by: Lohmeyer & Overby)
T10/09-174r0   Uploaded: 2009/05/05   98830 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-174r0.pdf
Minutes of CAP Working Group - May 5-7, 2009
(by: Weber & Lohmeyer)
T10/09-175r0   Uploaded: 2009/05/08   56873 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-175r0.htm
Minutes of CAP Working Group - May 5-7, 2009
(by: Weber & Lohmeyer)
T10/09-175r0   Uploaded: 2009/05/08   144925 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-175r0.pdf
SBC-3: On-disk Bitmap Support 2.0
(by: Roger Cummings)
T10/09-180r0   Uploaded: 2009/05/05   401959 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-180r0.pdf
SMC-3 Agenda for 4, May 2009 Bellevue WA
(by: Curtis Ballard)
T10/09-181r0   Uploaded: 2009/05/04   23616 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-181r0.pdf
ADC-3:	REPORT / SET SERVICE LOCATION Commands
(by: Paul Suhler)
T10/09-182r0   Uploaded: 2009/05/03   83757 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-182r0.pdf
ADC-3:	Service Location Information Management Protocol
(by: Paul Suhler)
T10/09-182r1   Uploaded: 2009/05/07   77935 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-182r1.pdf
SAS PHY - JTF Specification Improvement
(by: Mathieu Gagnon)
T10/09-183r0   Uploaded: 2009/05/05   162229 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-183r0.pdf
SAT-2: Letter ballot comment resolution incorporation document
(by: Mark Overby)
T10/09-184r0   Uploaded: 2009/05/04   2961453 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-184r0.fdf
SAT-2: Letter ballot comment resolution incorporation document
(by: Mark Overby)
T10/09-184r0   Uploaded: 2009/05/04   5412488 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-184r0.pdf
SAT-2: Letter ballot comment resolution incorporation document
(by: Mark Overby)
T10/09-184r1   Uploaded: 2009/05/07   3019236 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-184r1.fdf
SAT-2: Letter ballot comment resolution incorporation document
(by: Mark Overby)
T10/09-184r1   Uploaded: 2009/05/07   5406444 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-184r1.pdf
IEEE 1619 SISWG Liaison Report to T10, 2009-05
(by: Matthew V. Ball)
T10/09-186r0   Uploaded: 2009/05/06   72654 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-186r0.pdf
Minutes of FCP-4 Working Group - May 5, 2009
(by: David Peterson)
T10/09-187r0   Uploaded: 2009/05/05   84377 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-187r0.pdf
Minutes of SAS PHY Working Group, May 5, 2009
(by: Alvin Cox)
T10/09-188r0   Uploaded: 2009/05/05   30618 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-188r0.pdf
IETF Liaison Report to T10
(by: David Black)
T10/09-190r0   Uploaded: 2009/05/07   40692 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-190r0.pdf
SPC-4: Email on proving an SA in a CDB
(by: Kevin Butt)
T10/09-191r0   Uploaded: 2009/05/07   60440 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-191r0.pdf
STA/T10 Liaison Report 05/07/2009
(by: Michael Fitzpatrick)
T10/09-193r0   Uploaded: 2009/05/07   288513 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-193r0.pdf
Working Drafts
--------------
Automation/Drive Interface Commands - 3 (ADC-3)
(Editor: Paul Stone)
 Rev: 01       Uploaded: 2009/05/03   1064330 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=adc3r01.pdf
Serial Attached SCSI - 2.1 (SAS-2.1)
(Editor: Alvin Cox)
 Rev: 01       Uploaded: 2009/05/04   4470437 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=sas21-r01.pdf
Serial Attached SCSI - 2.1 (SAS-2.1)
(Editor: Alvin Cox)
 Rev: 01       Uploaded: 2009/05/04   3269566 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=sas21-r01.zip
SCSI / ATA Translation - 2 (SAT-2)
(Editor: Mark Overby)
 Rev: 07       Uploaded: 2009/05/04   1246915 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=sat2r07.pdf
SCSI / ATA Translation - 2 (SAT-2)
(Editor: Mark Overby)
 Rev: 07a      Uploaded: 2009/05/07   1254917 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=sat2r07a.pdf
(Report generated on 2009/05/10 at 00:00:50)
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From keiji_katata at post.pioneer.co.jp  Sun May 10 21:49:01 2009
From: keiji_katata at post.pioneer.co.jp (keiji_katata at post.pioneer.co.jp)
Date: Mon, 11 May 2009 13:49:01 +0900
Subject: June Fuji meeting information
Message-ID: <mailman.308.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* keiji_katata at post.pioneer.co.jp
*
Hello all,
In May MMC we decided that Fuji group has two days meeting 6/3,4 on June at
HLDS
Shibaura Tokyo Japan.
I will post an agenda proposal in this week.
Best regards,
Keiji Katata
PIONEER CORP.
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From scsi.bbs at lsi.com  Mon May 11 10:12:11 2009
From: scsi.bbs at lsi.com (T10 Voting Administrator)
Date: Mon, 11 May 2009 11:12:11 -0600
Subject: ADT-2: T10 Letter Ballot T10LBVOTE 09-197r0
Message-ID: <mailman.309.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* T10 Voting Administrator <scsi.bbs at lsi.com>
*
 2009/05/11 11:10:48
A T10 letter ballot (T10/09-197r0) has just been issued.
The topic of this letter ballot is:
  Forwarding ADT-2 to First Public Review
This ballot closes 2009/06/11 at 12:00 noon MDT.
If you are a T10 voting member, you should receive a separate
email with details of how to vote.
If you do not receive this email, it is likely that a spam
filter blocked its delivery. You can also find voting
instructions in the Members section of the T10 committee
web site.
Please do NOT reply to this automated email.
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From daviburg at windows.microsoft.com  Mon May 11 13:43:59 2009
From: daviburg at windows.microsoft.com (David Burg)
Date: Mon, 11 May 2009 13:43:59 -0700
Subject: MMC/Fuji: Proper way for device to fail a read/write streaming
 command?
Message-ID: <mailman.310.1441607349.22516.t10@sandbox.t10.org>

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

Hello,
While testing drives for Windows logo, we found that some write commands are
failing with sense information 02/04/08.
That is absolutely fine and actually desired with non-streaming writes.
However, some device also return this sense information to streaming write.
We are both wondering if this is legitimate - as the drive commits with
streaming to deliver a given throughput, respond promptly, etc. and if the
sense code 02/04/08 is the right one, or if it should be "UNIT
ATTENTION/INSUFFICIENT TIME FOR OPERATION" or something else.
Is a drive allowed to fail to complete a streaming read or write within a
short time, and if it is allowed, how the drive fail the command exactly?
With regards,
David.


From Paul.Stone at Quantum.Com  Mon May 11 15:15:24 2009
From: Paul.Stone at Quantum.Com (Paul Stone)
Date: Mon, 11 May 2009 16:15:24 -0600
Subject: ADT-2 Rev 6 letter ballot comments
Message-ID: <mailman.311.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* "Paul Stone" <Paul.Stone at Quantum.Com>
*
Automation/Drive Interface - Transport Protocol 2 (ADT-2) Rev 6 is in
letter ballot and available here:
http://www.t10.org/cgi-bin/ac.pl?t=f&f=adt2r06.pdf
The preferred format for letter ballot comments is an Adobe Acrobat .fdf
file.  If that option isn't available, text comments are acceptable
(please see the "Text Comments" section below).
When you place your vote, email the .fdf and/or .txt files to
lohmeyer at t10.org and paul.stone at quantum.com.
------------------------------------------------------------------------
-
NOT A T10 MEMBER?
=================
Comments are welcome from anyone.  Send them to me and I'll include them
in my own comment set.
.FDF COMMENTS
==============
.FDF comments may be generated with Adobe Acrobat.  If Adobe Acrobat is
not available to you, and you wish to use Adobe Reader to create
comments, please contact me (paul.stone at quantum.com).  I will need to
provide you with a PDF which supports Adobe Reader comments.
In Edit/Preferences/Commenting, please turn off "Create new pop-ups
aligned to the edge of the document" and turn on "Copy selected text
into Highlight,
Cross-Out, and Underline comment pop-ups."
Please do not use the "Text Edits" tools.
Please use the following tools:
1. The highlighting tools
  a) Highlighter tool (yellow)
  b) Cross-Out Text tool (red)
  c) Underline Text tool (green)
These associate a comment with specific words. Acrobat seeds the
comment with the selected text, which you can edit.
Use Highlighter when you're suggesting a change. Format the comment
as "<selected text> s/b <new text>" (s/b = should be)
Use Cross-Out Text when you're suggesting complete removal. Format the
comment as "remove <selected text>".  If the selected text is huge,
replace the innards with "..."
Use Underline Text if you have overlapping comments; it's an alternate
to the Highlighter tool.
If you're trying to select a link (e.g. "(see Table 37)"), select
some text around the link along with the link.	If you manage to
comment just the link text itself, then clicking on it will follow
the link rather than open the comment box.
2. The drawing markup tools
  a) Rectangle tool
  b) Oval tool
  c) and others
These associate a comment with specific areas on the page.  Use
these to highlight parts of figures or large sections of text.
3. Commenting tools
  a) Note tool (yellow)(Post-It Note)
This creates an arbitrary comment on a page, not associated
with any particular text.
COMMENT SUBSTANCE
=================
These guidelines apply to .FDF comments only.
The following information is _not_ necessary:
a) section number and name,
b) page numbers
c) editorial/technical
d) numbering of comments
If a comment applies to multiple sections, you can just place
one comment on the first occurrence and include all the
section numbers in the description.
If a comment is global, place it on any (preferably the first)
occurrence and add "Global":
    Global
    <substance of comment>
SAVING COMMENTS
===============
File/Export/Comments (Acrobat 5)
Comments/Export Comments/to File (Acrobat 7)
Comments/Export Comments to Data File (Acrobat 8)
Saves comments to a .fdf file.
File/Save
Saves the .pdf file with comments.
Comments/Summarize Comments
Creates a .pdf of comments only (or accompanying the original document).
Always use "Sort By Page."
TEXT COMMENTS
==============
When submitting text comments, please provide the following information,
each on a new line:
1. Company - Submitter Initials (optional) - comment number
	e.g., "QTM-JS-001" for Quantum, John Smith's comment #1
2. Identify the PDF page number. This is the number displayed by Acrobat
as "68 / 164".	Please do not use the page number printed in the
document.
3. Identify the section number.
4. Identify the figure or table.
5. Identify the paragraph/sentence or row/column to which the
   comment applies.
Examples:
    QTM-JS-001
    PDF page 90
    6.5.2 Service discovery message
    Table 41 - Service discovery message
    Third row
    <substance of comment>
    IBM-014
    PDF page 90
    6.5.2 Service discovery message
    First paragraph
    <substance of comment>
___________________________________
Paul Stone | Firmware Engineer | Quantum Corporation | Office:
949.725.1874 | paul.stone at quantum.com
___________________________________
Disregard the Quantum Corporation confidentiality notice below.  The
information contained in this transmission is not confidential.
Permission is hereby explicitly granted to disclose, copy, and further
distribute to any individual(s) or organization(s), without restriction.
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From Frederick.Knight at netapp.com  Tue May 12 06:21:39 2009
From: Frederick.Knight at netapp.com (Knight, Frederick)
Date: Tue, 12 May 2009 09:21:39 -0400
Subject: Old text in SBC3
Message-ID: <mailman.312.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* "Knight, Frederick" <Frederick.Knight at netapp.com>
*
sbc3r18 - 8.3.2.3.2 (last paragraph):
"If the Logical Unit descriptor includes the DEVICE TYPE SPECIFIC DATA
field, then the size of the DEVICE TYPE SPECIFIC DATA field shall be
12 bytes and the field shall contain data equivalent to that returned
by a successful READ CAPACITY command with LONGLBA bit set to one, and
the RELADR and PMI bits set to zero."
I looks like the LONGLBA bit was added and then removed in the 1999/2001
timeframe, and this text didn't get updated.
http://www.t10.org/cgi-bin/ac.pl?t=d&f=99-259r4.pdf
The returned data appears to be the same as the first 12 bytes of the
current READ CAPACITY (16) parameter data, so the fix looks easy:
"If the Logical Unit descriptor includes the DEVICE TYPE SPECIFIC DATA
field, then the size of the DEVICE TYPE SPECIFIC DATA field shall be
12 bytes and the field shall contain data equivalent to the first 12
bytes returned by a successful READ CAPACITY (16) command with the PMI
bit set to zero."
Any disagreement?
	Fred Knight
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From Frederick.Knight at netapp.com  Tue May 12 12:25:29 2009
From: Frederick.Knight at netapp.com (Knight, Frederick)
Date: Tue, 12 May 2009 15:25:29 -0400
Subject: Old text in SPC4
Message-ID: <mailman.313.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* "Knight, Frederick" <Frederick.Knight at netapp.com>
*
Resend to fix the reference (it's SPC, not SBC):
spc4r19 - 8.3.2.3.2 (last paragraph):
"If the Logical Unit descriptor includes the DEVICE TYPE SPECIFIC DATA
field, then the size of the DEVICE TYPE SPECIFIC DATA field shall be
12 bytes and the field shall contain data equivalent to that returned
by a successful READ CAPACITY command with LONGLBA bit set to one, and
the RELADR and PMI bits set to zero."
I looks like the LONGLBA bit was added and then removed in the 1999/2001
timeframe, and this text didn't get updated; RELADR doesn't exist
either.
http://www.t10.org/cgi-bin/ac.pl?t=d&f=99-259r4.pdf
The returned data appears to be the same as the first 12 bytes of the
current READ CAPACITY (16) parameter data, so the fix looks easy:
"If the Logical Unit descriptor includes the DEVICE TYPE SPECIFIC DATA
field, then the size of the DEVICE TYPE SPECIFIC DATA field shall be
12 bytes and the field shall contain data equivalent to the first 12
bytes returned by a successful READ CAPACITY (16) command with the PMI
bit set to zero."
These are reference to bits that don't exist anymore in the READ
CAPACITY
(or READ CAPACITY (16) command).  We shouldn't be referencing stuff that
doesn't exist.
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-200r0.pdf has the suggested
fix.
	Fred Knight
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From George.Penokie at lsi.com  Tue May 12 12:37:16 2009
From: George.Penokie at lsi.com (Penokie, George)
Date: Tue, 12 May 2009 13:37:16 -0600
Subject: Missing information in SP27:SAS_Settings state
Message-ID: <mailman.314.1441607349.22516.t10@sandbox.t10.org>

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

In the SP27:SAS_Settings state there is no information as to what the SP
transmitter should transmit after the Phy Capabilities Bits are transmitted
and before SNTT expires. The Phy Capabilities Bits transmitted message is
received from the SP transmitter into SP27 in the state machine figure but
there is not text description in the state description that uses that
message.
The requirement as shown in section 5.7.4.2.3.3 SNW-3 is to transmit D.C.
idle for the remainder of SNTT. This changes to transmit OOB idle for the
remainder of SNTT as a result of 08-439r3 being accepted.
I will add the following words to SP27 in SPL r2 as editorial as it will add
no new technical requirements to SPL:
After this state receives a Phy Capabilities Bits Transmitter message this
state shall transmit OOB idle.
If anyone has objections or would like different wording let me know by
tomorrow.
Bye for now,
George Penokie
LSI Corporation
3033 41st St. NW
Suite 100
Rochester, MN 55901
507-328-9017
george.penokie at lsi.com


From Elliott at hp.com  Tue May 12 13:28:11 2009
From: Elliott at hp.com (Elliott, Robert (Server Storage))
Date: Tue, 12 May 2009 20:28:11 +0000
Subject: Missing information in SP27:SAS_Settings state
Message-ID: <mailman.315.1441607349.22516.t10@sandbox.t10.org>

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

The SP transmitter and receiver section already covers that with "When not
otherwise instructed, the SP transmitter transmits D.C. idle."	Without that
rule, numerous other states would have to repeat the same rule, not just
SP27.  A few states (SP8, SP9, and SP28) that transmit nothing at all do say
"During this state D.C. idle shall be transmitted".  For consistency it's
probably simpler to delete those rather than try to add a similar rule to all
the other affected states.
Editorially, the SP state machine cannot "transmit OOB idle" - only the SP
transmitter does that.	There is no Transmit OOB Idle message defined for the
SP state machine to send to the SP transmitter, either.  That's the reason
for the passive wording in SP8, SP9, and SP28.
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Penokie,
George
Sent: Tuesday, May 12, 2009 2:37 PM
To: t10 at t10.org
Subject: Missing information in SP27:SAS_Settings state
In the SP27:SAS_Settings state there is no information as to what the SP
transmitter should transmit after the Phy Capabilities Bits are transmitted
and before SNTT expires. The Phy Capabilities Bits transmitted message is
received from the SP transmitter into SP27 in the state machine figure but
there is not text description in the state description that uses that
message.
The requirement as shown in section 5.7.4.2.3.3 SNW-3 is to transmit D.C.
idle for the remainder of SNTT. This changes to transmit OOB idle for the
remainder of SNTT as a result of 08-439r3 being accepted.
I will add the following words to SP27 in SPL r2 as editorial as it will add
no new technical requirements to SPL:
After this state receives a Phy Capabilities Bits Transmitter message this
state shall transmit OOB idle.
If anyone has objections or would like different wording let me know by
tomorrow.
Bye for now,
George Penokie
LSI Corporation
3033 41st St. NW
Suite 100
Rochester, MN 55901
507-328-9017
george.penokie at lsi.com


From keiji_katata at post.pioneer.co.jp  Tue May 12 23:24:40 2009
From: keiji_katata at post.pioneer.co.jp (keiji_katata at post.pioneer.co.jp)
Date: Wed, 13 May 2009 15:24:40 +0900
Subject: [MtFuji] MMC/Fuji: Proper way for device to fail a read/write streaming
 command?
Message-ID: <mailman.316.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* keiji_katata at post.pioneer.co.jp
*
PS.
I'm very sorry that a "not" was lost.
I think that the Streaming model does not cover data writing with a specific
bits rate.
Best regards,
Keiji Katata
PIONEER CORP.
Keiji Katata
2009/05/13 15:21
$B08 at h(B:  mtfuji5 at avc-pioneer.com
cc:    T10 Reflector <t10 at t10.org>
$B7oL>(B:  Re: [MtFuji] MMC/Fuji: Proper way for device to fail a
read/write
       streaming command?  (Document link: Keiji Katata)
Hi David,
Here are questions.
>commits with streaming to deliver a given throughput, respond promptly, etc.
Could you tell me your test environment?
>some device also return this sense information to streaming write.
Could you tell me when the drive reported 2/4/8? And why did you think that
this
is not desired?
I think that these information may be important to discuss your writing.
Here are comments.
I think that drive can report 2/4/8 on a write command with Streaming=1.
2/4/8
means that a drive buffer is full to receive the write command or a drive is
performing a higher priority job than the write command with Streaming=1 e.g.
OPC for the zone. When this OPC was failed the write command will be failed
with
Media error or some fatal error.
Streaming model of MMC/Fuji is designed for two purposes.
The 1st purposes that a system can allocate Continuos Data Area (CDA) on a
disc
zone. Streaming=1 write stops any reallocation of the data sector for the
CDA.
The 2nd purposes that a system can read a CDA with a desired bits rate and a
seek latency.
I think that the Streaming model does cover data writing with a specific bits
rate.
Best regards,
Keiji Katata
PIONEER CORP.
David Burg <daviburg at windows.microsoft.com>@avc-pioneer.com on 2009/05/12
05:43:59
mtfuji5 at avc-pioneer.com$B$KJV?.$7$F$/$@$5$$(B
$BAw?.<T(B:	  owner-mtfuji5 at avc-pioneer.com
$B08 at h(B: T10 Reflector <t10 at t10.org>, "mtfuji5 at avc-pioneer.com"
<mtfuji5 at avc-pioneer.com>
cc:
$B7oL>(B: [MtFuji] MMC/Fuji: Proper way for device to fail a read/write
streaming
command?
Hello,
While testing drives for Windows logo, we found that some write commands are
failing with sense information 02/04/08.
That is absolutely fine and actually desired with non-streaming writes.
However, some device also return this sense information to streaming write.
We
are both wondering if this is legitimate ? as the drive commits with
streaming
to deliver a given throughput, respond promptly, etc. and if the sense code
02/04/08 is the right one, or if it should be $B!H(BUNIT
ATTENTION/INSUFFICIENT TIME
FOR OPERATION$B!I(B or something else.
Is a drive allowed to fail to complete a streaming read or write within a
short
time, and if it is allowed, how the drive fail the command exactly?
With regards,
David.
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From keiji_katata at post.pioneer.co.jp  Tue May 12 23:21:20 2009
From: keiji_katata at post.pioneer.co.jp (keiji_katata at post.pioneer.co.jp)
Date: Wed, 13 May 2009 15:21:20 +0900
Subject: [MtFuji] MMC/Fuji: Proper way for device to fail a read/write streaming
 command?
Message-ID: <mailman.317.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* keiji_katata at post.pioneer.co.jp
*
Hi David,
Here are questions.
>commits with streaming to deliver a given throughput, respond promptly, etc.
Could you tell me your test environment?
>some device also return this sense information to streaming write.
Could you tell me when the drive reported 2/4/8? And why did you think that
this
is not desired?
I think that these information may be important to discuss your writing.
Here are comments.
I think that drive can report 2/4/8 on a write command with Streaming=1.
2/4/8
means that a drive buffer is full to receive the write command or a drive is
performing a higher priority job than the write command with Streaming=1 e.g.
OPC for the zone. When this OPC was failed the write command will be failed
with
Media error or some fatal error.
Streaming model of MMC/Fuji is designed for two purposes.
The 1st purposes that a system can allocate Continuos Data Area (CDA) on a
disc
zone. Streaming=1 write stops any reallocation of the data sector for the
CDA.
The 2nd purposes that a system can read a CDA with a desired bits rate and a
seek latency.
I think that the Streaming model does cover data writing with a specific bits
rate.
Best regards,
Keiji Katata
PIONEER CORP.
David Burg <daviburg at windows.microsoft.com>@avc-pioneer.com on 2009/05/12
05:43:59
mtfuji5 at avc-pioneer.com$B$KJV?.$7$F$/$@$5$$(B
$BAw?.<T(B:	  owner-mtfuji5 at avc-pioneer.com
$B08 at h(B: T10 Reflector <t10 at t10.org>, "mtfuji5 at avc-pioneer.com"
<mtfuji5 at avc-pioneer.com>
cc:
$B7oL>(B: [MtFuji] MMC/Fuji: Proper way for device to fail a read/write
streaming
command?
Hello,
While testing drives for Windows logo, we found that some write commands are
failing with sense information 02/04/08.
That is absolutely fine and actually desired with non-streaming writes.
However, some device also return this sense information to streaming write.
We
are both wondering if this is legitimate ? as the drive commits with
streaming
to deliver a given throughput, respond promptly, etc. and if the sense code
02/04/08 is the right one, or if it should be $B!H(BUNIT
ATTENTION/INSUFFICIENT TIME
FOR OPERATION$B!I(B or something else.
Is a drive allowed to fail to complete a streaming read or write within a
short
time, and if it is allowed, how the drive fail the command exactly?
With regards,
David.
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From kdbutt at us.ibm.com  Thu May 14 08:56:38 2009
From: kdbutt at us.ibm.com (Kevin D Butt)
Date: Thu, 14 May 2009 08:56:38 -0700
Subject: T10 Phone Conference for Proving SA ownership in a CDB
Message-ID: <mailman.318.1441607349.22516.t10@sandbox.t10.org>

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

IBM will be hosting a Phone conference to discuss Proving SA ownership in 
a CDB (09-140) on Monday May 18 from 8:00 AM - 9:00 AM PDT.
Phone (866) 907-1016
Participant Code 240180
If someone needs a phone number for outside the US please let me know and 
I will post it.
Thanks,
Kevin D. Butt
SCSI & Fibre Channel Architect, Tape Firmware
MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744
Tel: 520-799-5280
Fax: 520-799-2723 (T/L:321)
Email address: kdbutt at us.ibm.com


From kdbutt at us.ibm.com  Thu May 14 09:22:28 2009
From: kdbutt at us.ibm.com (Kevin D Butt)
Date: Thu, 14 May 2009 09:22:28 -0700
Subject: T10 Proving SA ownership in a CDB Phone Conference details
Message-ID: <mailman.319.1441607349.22516.t10@sandbox.t10.org>

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

 Hello,
I have added the web conference information for the May 18, 8:00 AM - 9:00 
AM PDT phone conference
IBM will be hosting a Web/Phone conference to discuss Proving SA ownership 
in a CDB (09-140) on Monday May 18 from 8:00 AM - 9:00 AM PDT.
Phone (866) 907-1016
Participant Code 240180
JOIN THE WEB CONFERENCE
1) Join the conference up to 20 minutes prior to 8:00 AM at 5/18/2009
2) Direct your web browser to the following URL: 
http://www-03.ibm.com/collaboration/webconferences/center/meetingdetails.jsp?
meetingId=49A5AAB9C7D4FA194CD114E167A74E41
3) When prompted, enter the web conference password: T10provingSA 
WEB CONFERENCE DETAILS:
Conference URL:
http://www-03.ibm.com/collaboration/webconferences/center/meetingdetails.jsp?
meetingId=49A5AAB9C7D4FA194CD114E167A74E41
Password:
T10provingSA 
Conference name:
T10 Phone Conference for Proving SA ownership in a CDB
Start time:
5/18/2009 8:00 AM
Duration:
01 hours 15 minutes
Meeting creator:
Kevin D. Butt 
Moderator:
Kevin D. Butt 
WHITEBOARD ATTACHMENTS:
No attachments 
PREPARE FOR THE WEB CONFERENCE
- Meeting participants
+ A userid and password is not required to enter the meeting.
+ A meeting password is required.
+ Browsers supported
     Internet Explorer 6.0 on Windows XP Professional
     Mozilla 1.7.12 on Windows XP Professional
     Mozilla 1.7.6 on RedHat Enterprise Linux 4.0 or Novell Linux Desktop 
9.0
     Firefox 1.5 on Windows XP Professional, RedHat Enterprise Linux 4.0, 
and Novell Linux Desktop 9.0
+ Java JDK/JRE supported
     IBM or Sun JDK/JRE 1.4.2 or later - Internet Explorer 6.0 on Windows 
XP Professional
     IBM or Sun JRE 1.4.2 or later - RedHat Enterprise Linux 4.0 and 
Novell Linux Desktop 9.0
     - To determine whether you have Java installed, and what version you 
have, for
       Microsoft (R) Internet Explorer, for example, click Tools - 
Internet Options, and then
       click Advanced. For other Microsoft(R) Windows(R)-based browsers, 
check the Java Control panel.
       IBM users can Download the latest version of Java from ISSI.
       External customers can Download the latest version of Java from Sun 
Microsystems
       Web site at http://www.java.sun.com 
     - Additional Browser setting Help can be found at :
https://www-03.ibm.com/collaboration/webconferences/center/stmtghelp/en/H_MAK
ING_YOUR_BROWSER_WORK_WITH_SAMETIME_3308_OVER.html
+ If this is your first IBM Web Conference, attend the special "test"
  meeting to make sure that you can join easily. Please visit
  http://www.ibm.com/collaboration/webconferences/center/meetingwizard.jsp
  and click "Attend a test meeting"
+ Help is available at
  http://www.ibm.com/collaboration/webconference/help/index.html
+ Leave the meeting or close your browser at the end of the meeting.
IBM Web Conferences is powered by the IBM Lotus Sametime product.
For more information on IBM's internal deployment of Sametime Web 
conferencing:
https://www-03.ibm.com/collaboration/webconference/help/what_features_functio
ns_enabled_IBM_wc_offering.html
For more information on the Lotus Sametime product: 
http://www.ibm.com/lotus/sametime 
To make a suggestion or ask questions, visit
  http://ibmforums.ibm.com/forums/forum.jspa?forumID=889 
Kevin D. Butt
SCSI & Fibre Channel Architect, Tape Firmware
MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744
Tel: 520-799-5280
Fax: 520-799-2723 (T/L:321)
Email address: kdbutt at us.ibm.com


From lohmeyer at t10.org  Thu May 14 10:36:05 2009
From: lohmeyer at t10.org (John Lohmeyer)
Date: Thu, 14 May 2009 11:36:05 -0600
Subject: T10 Reflector clean up
Message-ID: <mailman.320.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* John Lohmeyer <lohmeyer at t10.org>
*
#
#
#
#
#
#
#
#
#
#
It is time again to clean up the T10 Reflector. The following addresses have
bounced consistently since the last clean up and are being removed:
  Kris.Hartojo at lsi.com
  Akio.Yamazaki at sonynec-optiarc.com
  kanno at devm.crl.sony.co.jp
  Ross.Stenfort at lsi.com
  Ken.Paist at lsi.com
  bauld at lefthandnetworks.com
  Marian_Lakov at us.xyratex.com
  aendoh at easy.co.jp
  njohn at bri.hp.com
  hash at strg.sony.co.jp
  misaizu at strg.sony.co.jp
  kurt.kastein at lsi.com
  mdetwiler at digidata.com
  Ryuichiro.Tonari at roxio.com
  farzadk at suddenlink.net
  maki.yoshioka at pixela.co.jp
  matt at getcatalyst.com
  hiroyuki at cs.fujitsu.co.jp
  kamo at cs.fujitsu.co.jp
  umeda at cs.fujitsu.co.jp
  yorimitu at cs.fujitsu.co.jp
  h-nabe at cs.fujitsu.co.jp
  k-ohta at cs.fujitsu.co.jp
  Dongmei.Wang at am.sonynec-optiarc.com
  alexh at ulead.com
  liangjin at ulead.com
  kris.schoofs at scarlet.be
  Don.Grillo at taec.toshiba.com
  d_nagai at atg.mitsumi.co.jp
  dfhepner at us.ibm.com
  griffith at broadcom.com
These people may re-subscribe (hopefully, with a better address) by using the
following URL:
  http://www.t10.org/t10r.htm
--
John Lohmeyer		       Email: lohmeyer at t10.org
LSI Corp.		       Voice: +1-719-533-7560
4420 ArrowsWest Dr.		Cell: +1-719-338-1642
Colo Spgs, CO 80907
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From MOverby at nvidia.com  Thu May 14 11:01:27 2009
From: MOverby at nvidia.com (Mark Overby)
Date: Thu, 14 May 2009 11:01:27 -0700
Subject: SAT-2 r7b posted
Message-ID: <mailman.321.1441607349.22516.t10@sandbox.t10.org>

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

All clauses, including diagrams, through and including 6 are complete.
More postings to follow.
FDF posted as 09-184
-----------------------------------------------------------------------------
------
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.
-----------------------------------------------------------------------------
------


From keiji_katata at post.pioneer.co.jp  Fri May 15 01:42:29 2009
From: keiji_katata at post.pioneer.co.jp (keiji_katata at post.pioneer.co.jp)
Date: Fri, 15 May 2009 17:42:29 +0900
Subject: posted: June Mt.Fuji meeting agenda proposal
Message-ID: <mailman.322.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* keiji_katata at post.pioneer.co.jp
*
Hello all,
I posted agenda proposal on ftp.
 ftp.avc-pioneer.com/Mtfuji_7/Proposal/Jun09/DraftAgenda Jun09.pdf
To make sure the delivery of Intel's document, I also posted them on ftp.
 ftp.avc-pioneer.com/Mtfuji_7/Proposal/Jun09/
  MtFujiOverview.pdf
  MtFujiProposal_04_24_09.pdf
Best regards,
Keiji Katata
PIONEER CORP.
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From Paul.Suhler at quantum.com  Fri May 15 13:02:08 2009
From: Paul.Suhler at quantum.com (Paul Suhler)
Date: Fri, 15 May 2009 14:02:08 -0600
Subject: iADT-DISC Multicast Address Assigned
Message-ID: <mailman.323.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* "Paul Suhler" <Paul.Suhler at quantum.com>
*
This is to notify anyone who is interested in the iADT discovery
protocol (iADT-DISC) that IANA has assigned IPv4 and IPv6 multicast
addresses.  These are the final values for the two addresses in the
first paragraph of clause 6.5.3 of ADT-2 r6
(http://www.t10.org/cgi-bin/ac.pl?t=f&f=adt2r06.pdf).
Quantum will provide a letter ballot comment to update that clause with
these final values.
thanks,
Paul
___________________________________
Paul A. Suhler | Firmware Engineer | Quantum Corporation | Office:
949.856.7748 | paul.suhler at quantum.com 
-----Original Message-----
From: Amanda Baber via RT [mailto:iana-multicast at icann.org]
Sent: Tuesday, May 12, 2009 5:33 PM
To: Paul Suhler
Subject: [IANA #235172] Application for a Multicast Address 
Dear Paul,
IANA has assigned the following multicast addresses with you as the
point of
contact:
224.0.23.63	iADT Discovery
FF02:0:0:0:0:0:0:6F	iADT Discovery
Please see
http://www.iana.org/assignments/multicast-addresses/multicast-addresses.
xhtml
http://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-
addresses.xhtml
If you need to update the contact information, please send a message to
iana at iana.org.
Thanks,
Amanda Baber
IANA
----------------------------------------------------------------------
The information contained in this transmission may be confidential. Any
disclosure, copying, or further distribution of confidential information is
not permitted unless such privilege is explicitly granted in writing by
Quantum Corporation. Furthermore, Quantum Corporation is not responsible for
the proper and complete transmission of the substance of this communication
or for any delay in its receipt.
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From lohmeyer at t10.org  Sat May 16 23:00:55 2009
From: lohmeyer at t10.org (T10 Document Administrator)
Date: Sun, 17 May 2009 00:00:55 -0600
Subject: Recent T10 documents uploaded since 2009/05/10
Message-ID: <mailman.324.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* T10 Document Administrator <lohmeyer at t10.org>
*
Proposals
---------
Minutes SMC-3 Working Group May 04, 2009
(by: Kevin Butt)
T10/09-156r0   Uploaded: 2009/05/13   46605 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-156r0.pdf
SMC-3: Initializing VTL Replication
(by: Roger Cummings)
T10/09-179r1   Uploaded: 2009/05/12   140196 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-179r1.pdf
SAT-2: Letter ballot comment resolution incorporation document
(by: Mark Overby)
T10/09-184r2   Uploaded: 2009/05/14   3036753 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-184r2.fdf
SAT-2: Letter ballot comment resolution incorporation document
(by: Mark Overby)
T10/09-184r2   Uploaded: 2009/05/14   5434620 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-184r2.pdf
Symantec Patent Disclosure - Bitmaps on Disk
(by: Roger Cummings)
T10/09-185r0   Uploaded: 2009/05/12   163286 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-185r0.pdf
SSC-3: Resolution of LB IBM-021 (CORL and CORP)
(by: Kevin Butt)
T10/09-189r0   Uploaded: 2009/05/13   76843 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-189r0.pdf
Minutes: MMC WG Meeting Minutes, 6 and 7 May 2009
(by: William McFerrin)
T10/09-192r0   Uploaded: 2009/05/13   20607 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-192r0.pdf
Agenda for T10 Meeting #92 July 2009
(by: John Lohmeyer)
T10/09-194r0   Uploaded: 2009/05/11   62811 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-194r0.pdf
T10 Project Summary - May 2009
(by: John Lohmeyer)
T10/09-195r0   Uploaded: 2009/05/11   34243 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-195r0.pdf
Jeopardy Letter for July 2009 meeting
(by: John Lohmeyer)
T10/09-196r0   Uploaded: 2009/05/11   87631 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-196r0.pdf
Letter Ballot on forwarding ADT-2 to first public review
(by: John Lohmeyer)
T10/09-197r0   Uploaded: 2009/05/11   84699 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-197r0.pdf
SPC-4 Add IP Copy Engine service type to page 85h
(by: Frederick Knight)
T10/09-199r0   Uploaded: 2009/05/12   24917 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-199r0.pdf
SPC-4 Update Access Controls for READ CAPACITY(16)
(by: Ralph O. Weber)
T10/09-200r0   Uploaded: 2009/05/12   29287 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-200r0.pdf
Minutes SMC-3 May 13, 2009 phone conference
(by: Kevin Butt)
T10/09-201r0   Uploaded: 2009/05/13   44107 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-201r0.pdf
Obsolete commands and pages in SBC-3
(by: Ralph O. Weber)
T10/09-202r0   Uploaded: 2009/05/15   30148 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-202r0.pdf
Working Drafts
--------------
SCSI / ATA Translation - 2 (SAT-2)
(Editor: Mark Overby)
 Rev: 07b      Uploaded: 2009/05/14   1251279 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=sat2r07b.pdf
(Report generated on 2009/05/17 at 00:00:55)
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From lohmeyer at t10.org  Sun May 17 19:48:00 2009
From: lohmeyer at t10.org (John Lohmeyer)
Date: Sun, 17 May 2009 20:48:00 -0600
Subject: T10 Plenary minutes posted
Message-ID: <mailman.325.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* John Lohmeyer <lohmeyer at t10.org>
*
The draft minutes of the May 7th T10 meeting are available at:
  http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-176r0.htm
--
John Lohmeyer		       Email: lohmeyer at t10.org
LSI Corp.		       Voice: +1-719-533-7560
4420 ArrowsWest Dr.		Cell: +1-719-338-1642
Colo Spgs, CO 80907
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From kishore.k.karthikeyan at intel.com  Mon May 18 16:27:14 2009
From: kishore.k.karthikeyan at intel.com (Karthikeyan, Kishore K)
Date: Mon, 18 May 2009 16:27:14 -0700
Subject: SNW-3 SATA port selector confusion
Message-ID: <mailman.326.1441607349.22516.t10@sandbox.t10.org>

Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r0905180_f.htm">HTML-formatted message</a>
Attachment #1: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r0905180_08-283r1.pdf">08-283r1.pdf</a>

Please refer to the attached document
I have a question regarding this approved change to the SAS standard
(approved in July 2008)
The problem describes a scenario where PHY-B (which supports only SNW1) can
falsely detects a port selector due to the 1st COMWAKE it receives as part of
the PHY_CAPABILITIES bit of PHY-A (which supports only SNW3) in response to
PHY-A's COMINIT transmission after hotplug timeout.
Even though this problem looks real at first glance, can it ever really
happen? I say that because I think we are overlooking the fact that PHY-B
will restart OOB only after hotplug timeout which is 10ms minimum to a max of
500ms.
Lets look at the scenario in detail
If PHY-B detects that the SNW1 and SNW2 are both invalid, it will restart OOB
but ONLY after hotplug timeout (which can only be after a min of 10ms).
But PHY-A which supports only SNW3, will finish SNW-3 in RCDT (500us)+SNTT
(109us) = 610us and then restart OOB after hotplug timeout.
So while PHY-A is transmitting PHYCAP bit as part of SNW3, PHY-B is waiting
for hotplug timeout to expire. So by the time hotplug timeout of PHY-B
expires, PHY-A has already finished SNW3 and waiting for its own hotplug
timer to expire so that it can restart OOB.
So how can we ever hit the condition mentioned in this proposal? What am I
missing here?
Thanks in advance
Kishore
Intel Corporation


From Frederick.Knight at netapp.com  Tue May 19 11:11:40 2009
From: Frederick.Knight at netapp.com (Knight, Frederick)
Date: Tue, 19 May 2009 14:11:40 -0400
Subject: Thin Provisioning Thresholding
Message-ID: <mailman.327.1441607349.22516.t10@sandbox.t10.org>

Attachment #1: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r0905190_meeting_scheduled__thin_provisioning_thresholding.ics">meeting_scheduled__thin_provisioning_thresholding.ics</a>

The Thin Provisioning Thresholding document (09-011r4) has been posted
   http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-011r4.pdf
for review at tomorrows con-call.
A meeting invite is attached to add this event to your Outlook calendar.
	Fred Knight


From Alvin.Cox at seagate.com  Tue May 19 14:10:48 2009
From: Alvin.Cox at seagate.com (Alvin.Cox at seagate.com)
Date: Tue, 19 May 2009 16:10:48 -0500
Subject: SAS 2.1r02 has been posted
Message-ID: <mailman.328.1441607349.22516.t10@sandbox.t10.org>

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

See the draft standards section on the T10 site to obtain this update. 
Updates included for:
a) 08-439r3 SAS-2.1 / SPL An optical OOB method (Brian Day, LSI)
b) 09-098r5 SAS 2_1 Active Cable Electrical Characteristics (Gourgen 
Oganessyan, Quellan)
I know that 5.4.3.1 has an almost blank page because of the size of Table 
4. Since this table has several changes pending (adding HD connectors at a 
minimum), I plan to address the formatting issues when the connector 
situation gets settled.
Left margin change bars are included.
Alvin Cox
Seagate Technology, LLC
Office 405-392-3738
Cell 405-206-4809


From keiji_katata at post.pioneer.co.jp  Wed May 20 01:09:46 2009
From: keiji_katata at post.pioneer.co.jp (keiji_katata at post.pioneer.co.jp)
Date: Wed, 20 May 2009 17:09:46 +0900
Subject: posted: material for agenda item 8.3
Message-ID: <mailman.329.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* keiji_katata at post.pioneer.co.jp
*
Hello all,
As an editor, I made documents for agenda item 8.3 and posted them on ftp.
ftp.avc-pioneer.com/Mtfuji_7/Proposal/Jun09/
 GET_CONFIGURATION-DB.pdf
 GET_EVENT_STATUS_NOTIFICATION-DB.pdf
Best regards,
Keiji Katata
PIONEER CORP.
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From Kevin_Marks at Dell.com  Wed May 20 09:11:08 2009
From: Kevin_Marks at Dell.com (Kevin_Marks at Dell.com)
Date: Wed, 20 May 2009 11:11:08 -0500
Subject: For TP Call Today
Message-ID: <mailman.330.1441607349.22516.t10@sandbox.t10.org>

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

Topic:	  Thin Provisioning Thresholding 
Date:	  Wednesday, May 20, 2009 
Time:	  9:00 am, Pacific Daylight Time (GMT -07:00, San Francisco) 
Meeting number: 	   925 302 141 
Meeting password:	  TP 
To view or edit your meeting information, please log into your WebEx
account at http://netapp-meeting.webex.com
<http://netapp-meeting.webex.com&gt; , and click on "My WebEx."
To start your meeting, log into your WebEx account, click on "My WebEx"
and click on "Start" next to your meeting. 
Attendees will be able to join your meeting by clicking on the link that
was given to them in an automatically generated e-mail WebEx sent to all
of your attendees. 
Teleconference: 1-888-765-3653
Conf ID 595-2226# 


From Alvin.Cox at seagate.com  Wed May 20 11:10:26 2009
From: Alvin.Cox at seagate.com (Alvin.Cox at seagate.com)
Date: Wed, 20 May 2009 13:10:26 -0500
Subject: Reminder: SAS-2.1 PHY WG teleconference, 5/21, 10:00 am CDT
Message-ID: <mailman.331.1441607349.22516.t10@sandbox.t10.org>

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

Agenda:
Discuss removal of 4x external connectors (infiniband) from SAS 2.1
Proposals for intelligent cable interfaces
SAS PHY - JTF Specification Improvement (09-183r0) [Gagnon]
New items
The mini SAS HD proposal is not ready yet. I hope to have it posted before 
the next call.
Teleconference April 23, 2009 10:00 am CDT 
USA Toll Free Dial in Number: (877)810-9442 
International Access/Caller Paid Dial In Number: (636)651-3190 
PARTICIPANT CODE: 3243413 
WEBEX:
Topic: SAS-2.1 PHY WG 
Date: Thursday, May 21, 2009 
Time: 10:00 am, Central Daylight Time (GMT -05:00, Chicago) 
Meeting Number: 826 515 680 
Meeting Password: newsas 
Please click the link below to see more information about the meeting, 
including its agenda, or to join the meeting. 
------------------------------------------------------- 
To join the online meeting (Now from iPhones too!) 
------------------------------------------------------- 
1. Go to 
https://seagate.webex.com/seagate/j.php?ED=90748572&UID=0&PW=a3c3e3240b5e4847
232e23 
2. Enter your name and email address. 
3. Enter the meeting password: newsas 
4. Click "Join Now". 
5. Follow the instructions that appear on your screen. 
------------------------------------------------------- 
For assistance 
------------------------------------------------------- 
1. Go to https://seagate.webex.com/seagate/mc 
2. On the left navigation bar, click "Support". 
To update this meeting to your calendar program (for example Microsoft 
Outlook), click this link: 
https://seagate.webex.com/seagate/j.php?ED=90748572&UID=0&ICS=UMI&LD=1&RD=2&S
T=1&SHA2=SVyTzTdCGzSIxsgaH07Ohz1skP261RTOA-QjHZRNW6c= 
WebEx will automatically setup Meeting Manager for Windows the first time 
you join a meeting. To save time, you can setup prior to the meeting by 
clicking this link: 
https://seagate.webex.com/seagate/meetingcenter/mcsetup.php 
Alvin Cox
Seagate Technology, LLC
Office 405-392-3738
Cell 405-206-4809


From kishore.k.karthikeyan at intel.com  Wed May 20 12:06:06 2009
From: kishore.k.karthikeyan at intel.com (Karthikeyan, Kishore K)
Date: Wed, 20 May 2009 12:06:06 -0700
Subject: SNW-3 SATA port selector confusion
Message-ID: <mailman.332.1441607349.22516.t10@sandbox.t10.org>

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

Hi
I hope atleast some people have got the chance to read through this email and
understand the issue at hand.
Again I will try to put the question in a different way to solicit some
response :)
If I don't implement this new arc in the SP statemachine (dc_idle detection
after SNW2), can I hit the discrepancy mentioned in this proposal (wrongly
detecting port selector attached) with valid speed negotiation scenarios? And
if I cannot hit this condition ever, do I really need to incorporate
unnecessary additional logic into the design?
Thanks
Kishore
________________________________
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Karthikeyan,
Kishore K
Sent: Monday, May 18, 2009 4:27 PM
To: t10 at t10.org
Subject: SNW-3 SATA port selector confusion
Please refer to the attached document
I have a question regarding this approved change to the SAS standard
(approved in July 2008)
The problem describes a scenario where PHY-B (which supports only SNW1) can
falsely detects a port selector due to the 1st COMWAKE it receives as part of
the PHY_CAPABILITIES bit of PHY-A (which supports only SNW3) in response to
PHY-A's COMINIT transmission after hotplug timeout.
Even though this problem looks real at first glance, can it ever really
happen? I say that because I think we are overlooking the fact that PHY-B
will restart OOB only after hotplug timeout which is 10ms minimum to a max of
500ms.
Lets look at the scenario in detail
If PHY-B detects that the SNW1 and SNW2 are both invalid, it will restart OOB
but ONLY after hotplug timeout (which can only be after a min of 10ms).
But PHY-A which supports only SNW3, will finish SNW-3 in RCDT (500us)+SNTT
(109us) = 610us and then restart OOB after hotplug timeout.
So while PHY-A is transmitting PHYCAP bit as part of SNW3, PHY-B is waiting
for hotplug timeout to expire. So by the time hotplug timeout of PHY-B
expires, PHY-A has already finished SNW3 and waiting for its own hotplug
timer to expire so that it can restart OOB.
So how can we ever hit the condition mentioned in this proposal? What am I
missing here?
Thanks in advance
Kishore
Intel Corporation


From Brian.Day at lsi.com  Wed May 20 13:30:07 2009
From: Brian.Day at lsi.com (Day, Brian)
Date: Wed, 20 May 2009 14:30:07 -0600
Subject: SNW-3 SATA port selector confusion
Message-ID: <mailman.333.1441607349.22516.t10@sandbox.t10.org>

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

Hi Kishore...
You're statement below here is correct:
"So while PHY-A is transmitting PHYCAP bit as part of SNW3, PHY-B is waiting
for hotplug timeout to expire."
Phy-B waiting for hot-plug to expire means it is in the SP1:OOB_AwaitCOMX
state.	Referring back to the SAS-1.1 spec for that state indicates that if a
COMWAKE is received in this state, that phy asserts the ATTACHED SATA PORT
SELECTOR bit.
I think this is the condition that the proposal tried to address.
Brian Day
LSI Corp.
________________________________
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Karthikeyan,
Kishore K
Sent: Wednesday, May 20, 2009 1:06 PM
To: t10 at t10.org
Subject: RE: SNW-3 SATA port selector confusion
Hi
I hope atleast some people have got the chance to read through this email and
understand the issue at hand.
Again I will try to put the question in a different way to solicit some
response :)
If I don't implement this new arc in the SP statemachine (dc_idle detection
after SNW2), can I hit the discrepancy mentioned in this proposal (wrongly
detecting port selector attached) with valid speed negotiation scenarios? And
if I cannot hit this condition ever, do I really need to incorporate
unnecessary additional logic into the design?
Thanks
Kishore
________________________________
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Karthikeyan,
Kishore K
Sent: Monday, May 18, 2009 4:27 PM
To: t10 at t10.org
Subject: SNW-3 SATA port selector confusion
Please refer to the attached document
I have a question regarding this approved change to the SAS standard
(approved in July 2008)
The problem describes a scenario where PHY-B (which supports only SNW1) can
falsely detects a port selector due to the 1st COMWAKE it receives as part of
the PHY_CAPABILITIES bit of PHY-A (which supports only SNW3) in response to
PHY-A's COMINIT transmission after hotplug timeout.
Even though this problem looks real at first glance, can it ever really
happen? I say that because I think we are overlooking the fact that PHY-B
will restart OOB only after hotplug timeout which is 10ms minimum to a max of
500ms.
Lets look at the scenario in detail
If PHY-B detects that the SNW1 and SNW2 are both invalid, it will restart OOB
but ONLY after hotplug timeout (which can only be after a min of 10ms).
But PHY-A which supports only SNW3, will finish SNW-3 in RCDT (500us)+SNTT
(109us) = 610us and then restart OOB after hotplug timeout.
So while PHY-A is transmitting PHYCAP bit as part of SNW3, PHY-B is waiting
for hotplug timeout to expire. So by the time hotplug timeout of PHY-B
expires, PHY-A has already finished SNW3 and waiting for its own hotplug
timer to expire so that it can restart OOB.
So how can we ever hit the condition mentioned in this proposal? What am I
missing here?
Thanks in advance
Kishore
Intel Corporation


From kishore.k.karthikeyan at intel.com  Wed May 20 14:23:09 2009
From: kishore.k.karthikeyan at intel.com (Karthikeyan, Kishore K)
Date: Wed, 20 May 2009 14:23:09 -0700
Subject: SNW-3 SATA port selector confusion
Message-ID: <mailman.334.1441607349.22516.t10@sandbox.t10.org>

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

Thanks Brian for helping me understand the problem. I should not have
overlooked this important piece of information.
Fig 159 in sas2r15 threw me off guard because I saw the hot-plug timeout
followed by the COMINIT transmitted by PHY-B and I failed to check which
state it would be in when it is waiting for hotplug timer to expire.
Appreciate your help
Kishore
________________________________
From: Day, Brian [mailto:Brian.Day at lsi.com]
Sent: Wednesday, May 20, 2009 1:30 PM
To: Karthikeyan, Kishore K; t10 at t10.org
Subject: RE: SNW-3 SATA port selector confusion
Hi Kishore...
You're statement below here is correct:
"So while PHY-A is transmitting PHYCAP bit as part of SNW3, PHY-B is waiting
for hotplug timeout to expire."
Phy-B waiting for hot-plug to expire means it is in the SP1:OOB_AwaitCOMX
state.	Referring back to the SAS-1.1 spec for that state indicates that if a
COMWAKE is received in this state, that phy asserts the ATTACHED SATA PORT
SELECTOR bit.
I think this is the condition that the proposal tried to address.
Brian Day
LSI Corp.
________________________________
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Karthikeyan,
Kishore K
Sent: Wednesday, May 20, 2009 1:06 PM
To: t10 at t10.org
Subject: RE: SNW-3 SATA port selector confusion
Hi
I hope atleast some people have got the chance to read through this email and
understand the issue at hand.
Again I will try to put the question in a different way to solicit some
response :)
If I don't implement this new arc in the SP statemachine (dc_idle detection
after SNW2), can I hit the discrepancy mentioned in this proposal (wrongly
detecting port selector attached) with valid speed negotiation scenarios? And
if I cannot hit this condition ever, do I really need to incorporate
unnecessary additional logic into the design?
Thanks
Kishore
________________________________
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Karthikeyan,
Kishore K
Sent: Monday, May 18, 2009 4:27 PM
To: t10 at t10.org
Subject: SNW-3 SATA port selector confusion
Please refer to the attached document
I have a question regarding this approved change to the SAS standard
(approved in July 2008)
The problem describes a scenario where PHY-B (which supports only SNW1) can
falsely detects a port selector due to the 1st COMWAKE it receives as part of
the PHY_CAPABILITIES bit of PHY-A (which supports only SNW3) in response to
PHY-A's COMINIT transmission after hotplug timeout.
Even though this problem looks real at first glance, can it ever really
happen? I say that because I think we are overlooking the fact that PHY-B
will restart OOB only after hotplug timeout which is 10ms minimum to a max of
500ms.
Lets look at the scenario in detail
If PHY-B detects that the SNW1 and SNW2 are both invalid, it will restart OOB
but ONLY after hotplug timeout (which can only be after a min of 10ms).
But PHY-A which supports only SNW3, will finish SNW-3 in RCDT (500us)+SNTT
(109us) = 610us and then restart OOB after hotplug timeout.
So while PHY-A is transmitting PHYCAP bit as part of SNW3, PHY-B is waiting
for hotplug timeout to expire. So by the time hotplug timeout of PHY-B
expires, PHY-A has already finished SNW3 and waiting for its own hotplug
timer to expire so that it can restart OOB.
So how can we ever hit the condition mentioned in this proposal? What am I
missing here?
Thanks in advance
Kishore
Intel Corporation


From Frederick.Knight at netapp.com  Fri May 22 06:18:52 2009
From: Frederick.Knight at netapp.com (Knight, Frederick)
Date: Fri, 22 May 2009 09:18:52 -0400
Subject: FW:  Meeting: Thin Provisioning Thresholding
Message-ID: <mailman.335.1441607349.22516.t10@sandbox.t10.org>

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

Below is the information about the second TP con-call.
________________________________
From: frederick knight [mailto:messenger at webex.com] 
Sent: Thursday, May 21, 2009 5:44 PM
To: Knight, Frederick
Subject: Meeting: Thin Provisioning Thresholding
Hello , 
frederick knight has invited you to join a meeting on the Web, using
WebEx 
Topic: Thin Provisioning Thresholding 
Date: Friday, June 12, 2009 
Time: 1:00 pm, Eastern Daylight Time (GMT -04:00, New York) 
Meeting number: 925 018 582 
Meeting password: TP 
Please click the link below to see more information, or to join the
meeting. 
NOTE: You do not need to register for a WebEx Account to attend this
meeting. Just click on the link below and use the Meeting password: TP 
https://netapp-meeting.webex.com/netapp-meeting/j.php?ED=118332092&UID=0
&PW=4b27eda3ea1a03 
Teleconference: 1-888-765-3653 
Conf ID 595-2226# 
To contact frederick knight, 
send a message to this address: knight at netapp.com 


From Frederick.Knight at netapp.com  Fri May 22 06:19:17 2009
From: Frederick.Knight at netapp.com (Knight, Frederick)
Date: Fri, 22 May 2009 09:19:17 -0400
Subject: FW:  Meeting: Thin Provisioning Thresholding
Message-ID: <mailman.336.1441607349.22516.t10@sandbox.t10.org>

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

Below is the information about the third TP con-call.
________________________________
From: frederick knight [mailto:messenger at webex.com] 
Sent: Thursday, May 21, 2009 5:46 PM
To: Knight, Frederick
Subject: Meeting: Thin Provisioning Thresholding
Hello , 
frederick knight has invited you to join a meeting on the Web, using
WebEx 
Topic: Thin Provisioning Thresholding 
Date: Wednesday, June 24, 2009 
Time: 3:00 pm, Eastern Daylight Time (GMT -04:00, New York) 
Meeting number: 926 656 196 
Meeting password: TP 
Please click the link below to see more information, or to join the
meeting. 
NOTE: You do not need to register for a WebEx Account to attend this
meeting. Just click on the link below and use the Meeting password: TP 
https://netapp-meeting.webex.com/netapp-meeting/j.php?ED=118332167&UID=0
&PW=a77f8674601b00 
Teleconference: 1-888-765-3653 
Conf ID 595-2226# 
To contact frederick knight, 
send a message to this address: knight at netapp.com 


From Frederick.Knight at netapp.com  Fri May 22 09:34:12 2009
From: Frederick.Knight at netapp.com (Knight, Frederick)
Date: Fri, 22 May 2009 12:34:12 -0400
Subject: Interesting "uninterrupted sequence" question
Message-ID: <mailman.337.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* "Knight, Frederick" <Frederick.Knight at netapp.com>
*
It is well understood that multiple concurrent overlapping commands can
interfere with each other.  For example, if I have 2 successful
concurrent SIMPLE tagged WRITE commands as follows:
1) WRITE 0s to LBA 1,2,3
2) WRITE 1s to LBA 1,2,3
There is no guarantee what will be in LBAs 1,2,3.  It could be 0s in
some of those LBAs, or 1s in some of those LBAs.  The device could
legally do the following:
WRITE 0s to LBA 1,3
WRITE 1s to LBA 1,3
seek to get to LBA 2 (maybe LBA 2 got revectored)
WRITE 1s to LBA 2
WRITE 0s to LBA 2
So a READ of LBA 1,2,3 would not get all 0s or all 1s, it would get
whatever was the result of the interaction of those 2 overlapping WRITE
commands.  It is the responsibility of the application client to used
ORDERED commands or other means to create the consistency it needs.
Now, along comes ORWRITE, XDWRITE, XPWRITE, and other commands with an
"uninterruptable series of actions".
It seems clear that these "uninterruptable" actions can be ABORTed, so
in fact, some interruptions can occur.	I interpret the uninterruptable
nature to relate to the above case (multiple concurrent overlapping
commands that are also required to be uninterruptable).
So, change the above case to ORWRITEs (with an initial state of all
zeros in LBAs 1,2,3):
1) ORWRITE 1 into each LBA 1,2,3
2) ORWRITE 2 into each LBA 1,2,3
Because both commands are "uninterruptable" then I know, that when both
commmands complete, and I READ LBA 1,2,3 each LBA will contain 3 (1 and
2 will each be "OR"ed into each block).  I will not find the value 1 or
2 in any of those LBAs.  Because of the uninterruptable series of
actions, the result is as if the commands had been ORDERED commands.
So, next, what happens when I MIX overlapping concurrent uninterruptable
with interruptable commands?  Consider (again SIMPLE tagged, and an
initial state of all zeros in LBAs 1,2,3):
1) READ LBA 1,2,3 (transfer data for LBA 1,3)
2) ORWRITE 1 into each LBA 1,2,3
3) (transfer data for LBA 2 and complete READ command)
I assume since the READ is not required to be uninterruptable, it
operates just like the first case.  While the ORWRITE is executing, the
READ can continue to execute, so the READ could return some of those
LBAs with 0 in them, and some of those LBAs with 1 in them.
The consistency of an uninterrupted series of actions is only protected
/ guaranteed in relation to the actions of other overlapping
uninterrupted series of actions.
Is this generally agreed?  If not, this may become a July discussion
item.
	Fred Knight
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From roweber at IEEE.org  Fri May 22 11:22:18 2009
From: roweber at IEEE.org (Ralph Weber)
Date: Fri, 22 May 2009 13:22:18 -0500
Subject: SPC-4 r20 posted
Message-ID: <mailman.338.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* Ralph Weber <roweber at ieee.org>
*
I have uploaded an SPC-4 revision that incorporates all
approved proposals.
http://www.t10.org/cgi-bin/ac.pl?t=f&f=spc4r20.pdf
Naturally, I could not resist tweaking them a little bit,
but the proposal authors (all two of you) ought to be
able to recognize their handiwork next to the change bars.
All the best,
.Ralph
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From Gerry.Houlder at seagate.com  Fri May 22 12:56:04 2009
From: Gerry.Houlder at seagate.com (Gerry.Houlder at seagate.com)
Date: Fri, 22 May 2009 14:56:04 -0500
Subject: Interesting "uninterrupted sequence" question
Message-ID: <mailman.339.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* Gerry.Houlder at seagate.com
*
I think SCSI promises a little more than what you describe. A SCSI device
might choose to reorder commands 1 and 2, but it shall complete each
command before doing an overlapping command. My customers would tell me I
have a broken product if they sent two consequetive writes (0 and 1), both
completed with GOOD status,  and some blocks had pattern 0 and some had
pattern 1.
	     "Knight,							   
	     Frederick" 						   
	     <Frederick.Knight						To 
	     @netapp.com>	       <t10 at t10.org>			   
	     Sent by:							cc 
	     owner-t10 at t10.org						   
	     No Phone Info					   Subject 
	     Available		       Interesting "uninterrupted	   
				       sequence" question		   
	     05/22/2009 11:34						   
	     AM 							   
* From the T10 Reflector (t10 at t10.org), posted by:
* "Knight, Frederick" <Frederick.Knight at netapp.com>
*
It is well understood that multiple concurrent overlapping commands can
interfere with each other.  For example, if I have 2 successful
concurrent SIMPLE tagged WRITE commands as follows:
1) WRITE 0s to LBA 1,2,3
2) WRITE 1s to LBA 1,2,3
There is no guarantee what will be in LBAs 1,2,3.  It could be 0s in
some of those LBAs, or 1s in some of those LBAs.  The device could
legally do the following:
WRITE 0s to LBA 1,3
WRITE 1s to LBA 1,3
seek to get to LBA 2 (maybe LBA 2 got revectored)
WRITE 1s to LBA 2
WRITE 0s to LBA 2
So a READ of LBA 1,2,3 would not get all 0s or all 1s, it would get
whatever was the result of the interaction of those 2 overlapping WRITE
commands.  It is the responsibility of the application client to used
ORDERED commands or other means to create the consistency it needs.
Now, along comes ORWRITE, XDWRITE, XPWRITE, and other commands with an
"uninterruptable series of actions".
It seems clear that these "uninterruptable" actions can be ABORTed, so
in fact, some interruptions can occur.	I interpret the uninterruptable
nature to relate to the above case (multiple concurrent overlapping
commands that are also required to be uninterruptable).
So, change the above case to ORWRITEs (with an initial state of all
zeros in LBAs 1,2,3):
1) ORWRITE 1 into each LBA 1,2,3
2) ORWRITE 2 into each LBA 1,2,3
Because both commands are "uninterruptable" then I know, that when both
commmands complete, and I READ LBA 1,2,3 each LBA will contain 3 (1 and
2 will each be "OR"ed into each block).  I will not find the value 1 or
2 in any of those LBAs.  Because of the uninterruptable series of
actions, the result is as if the commands had been ORDERED commands.
So, next, what happens when I MIX overlapping concurrent uninterruptable
with interruptable commands?  Consider (again SIMPLE tagged, and an
initial state of all zeros in LBAs 1,2,3):
1) READ LBA 1,2,3 (transfer data for LBA 1,3)
2) ORWRITE 1 into each LBA 1,2,3
3) (transfer data for LBA 2 and complete READ command)
I assume since the READ is not required to be uninterruptable, it
operates just like the first case.  While the ORWRITE is executing, the
READ can continue to execute, so the READ could return some of those
LBAs with 0 in them, and some of those LBAs with 1 in them.
The consistency of an uninterrupted series of actions is only protected
/ guaranteed in relation to the actions of other overlapping
uninterrupted series of actions.
Is this generally agreed?  If not, this may become a July discussion
item.
	     Fred Knight
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From roweber at IEEE.org  Sat May 23 04:59:55 2009
From: roweber at IEEE.org (Ralph Weber)
Date: Sat, 23 May 2009 06:59:55 -0500
Subject: Interesting "uninterrupted sequence" question
Message-ID: <mailman.340.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* Ralph Weber <roweber at ieee.org>
*
Gerry,
Would it be correct to assume that the disks which you describe
return 0h in the Queue Algorithm Modifier field in the Control
Mode Page?
Many SCSI purists with whom I have conversed over the years have
claimed that, if the Queue Algorithm Modifier is set to 1h, then
the "some blocks with pattern 0 and some blocks with pattern 1"
result is allowed.
All the best,
.Ralph
Gerry.Houlder at seagate.com wrote:
> * From the T10 Reflector (t10 at t10.org), posted by:
> * Gerry.Houlder at seagate.com
> *
> I think SCSI promises a little more than what you describe. A SCSI device
> might choose to reorder commands 1 and 2, but it shall complete each
> command before doing an overlapping command. My customers would tell me I
> have a broken product if they sent two consequetive writes (0 and 1), both
> completed with GOOD status,  and some blocks had pattern 0 and some had
> pattern 1.
>
>
>
>									     
>	       "Knight, 						     
>	       Frederick"						     
>	       <Frederick.Knight					  To 
>	       @netapp.com>		 <t10 at t10.org>			     
>	       Sent by: 						  cc 
>	       owner-t10 at t10.org					     
>	       No Phone Info					     Subject 
>	       Available		 Interesting "uninterrupted	     
>					 sequence" question		     
>									     
>	       05/22/2009 11:34 					     
>	       AM							     
>									     
>									     
>									     
>
>
>
>
> * From the T10 Reflector (t10 at t10.org), posted by:
> * "Knight, Frederick" <Frederick.Knight at netapp.com>
> *
> It is well understood that multiple concurrent overlapping commands can
> interfere with each other.  For example, if I have 2 successful
> concurrent SIMPLE tagged WRITE commands as follows:
>
> 1) WRITE 0s to LBA 1,2,3
> 2) WRITE 1s to LBA 1,2,3
>
> There is no guarantee what will be in LBAs 1,2,3.  It could be 0s in
> some of those LBAs, or 1s in some of those LBAs.  The device could
> legally do the following:
>
> WRITE 0s to LBA 1,3
> WRITE 1s to LBA 1,3
> seek to get to LBA 2 (maybe LBA 2 got revectored)
> WRITE 1s to LBA 2
> WRITE 0s to LBA 2
>
> So a READ of LBA 1,2,3 would not get all 0s or all 1s, it would get
> whatever was the result of the interaction of those 2 overlapping WRITE
> commands.  It is the responsibility of the application client to used
> ORDERED commands or other means to create the consistency it needs.
>
> Now, along comes ORWRITE, XDWRITE, XPWRITE, and other commands with an
> "uninterruptable series of actions".
>
> It seems clear that these "uninterruptable" actions can be ABORTed, so
> in fact, some interruptions can occur.  I interpret the uninterruptable
> nature to relate to the above case (multiple concurrent overlapping
> commands that are also required to be uninterruptable).
>
> So, change the above case to ORWRITEs (with an initial state of all
> zeros in LBAs 1,2,3):
>
> 1) ORWRITE 1 into each LBA 1,2,3
> 2) ORWRITE 2 into each LBA 1,2,3
>
> Because both commands are "uninterruptable" then I know, that when both
> commmands complete, and I READ LBA 1,2,3 each LBA will contain 3 (1 and
> 2 will each be "OR"ed into each block).  I will not find the value 1 or
> 2 in any of those LBAs.  Because of the uninterruptable series of
> actions, the result is as if the commands had been ORDERED commands.
>
> So, next, what happens when I MIX overlapping concurrent uninterruptable
> with interruptable commands?	Consider (again SIMPLE tagged, and an
> initial state of all zeros in LBAs 1,2,3):
>
> 1) READ LBA 1,2,3 (transfer data for LBA 1,3)
> 2) ORWRITE 1 into each LBA 1,2,3
> 3) (transfer data for LBA 2 and complete READ command)
>
> I assume since the READ is not required to be uninterruptable, it
> operates just like the first case.  While the ORWRITE is executing, the
> READ can continue to execute, so the READ could return some of those
> LBAs with 0 in them, and some of those LBAs with 1 in them.
>
> The consistency of an uninterrupted series of actions is only protected
> / guaranteed in relation to the actions of other overlapping
> uninterrupted series of actions.
>
> Is this generally agreed?  If not, this may become a July discussion
> item.
>
>	       Fred Knight
>
>
>
> *
> * For T10 Reflector information, send a message with
> * 'info t10' (no quotes) in the message body to majordomo at t10.org
>
>
> *
> * For T10 Reflector information, send a message with
> * 'info t10' (no quotes) in the message body to majordomo at t10.org
>
>
>
>   
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From Frederick.Knight at netapp.com  Sat May 23 07:25:46 2009
From: Frederick.Knight at netapp.com (Knight, Frederick)
Date: Sat, 23 May 2009 10:25:46 -0400
Subject: Interesting "uninterrupted sequence" question
Message-ID: <mailman.341.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* "Knight, Frederick" <Frederick.Knight at netapp.com>
*
The commands are concurrent, they are SIMPLE tagged, and Queue Algorithm
Modifier=1 (I forgot to mention that earlier). 
I agree, if QAM=0, then they must act as ORDERED commands, so what you
say is true (at least for a single I_T nexus).
	Fred
-----Original Message-----
From: Gerry.Houlder at seagate.com [mailto:Gerry.Houlder at seagate.com] 
Sent: Friday, May 22, 2009 3:56 PM
To: t10 at t10.org
Subject: Re: Interesting "uninterrupted sequence" question
* From the T10 Reflector (t10 at t10.org), posted by:
* Gerry.Houlder at seagate.com
*
I think SCSI promises a little more than what you describe. A SCSI
device might choose to reorder commands 1 and 2, but it shall complete
each command before doing an overlapping command. My customers would
tell me I have a broken product if they sent two consequetive writes (0
and 1), both completed with GOOD status,  and some blocks had pattern 0
and some had pattern 1.
	     "Knight,
	     Frederick"
	     <Frederick.Knight
To 
	     @netapp.com>	       <t10 at t10.org>
	     Sent by:
cc 
	     owner-t10 at t10.org
	     No Phone Info
Subject 
	     Available		       Interesting "uninterrupted
				       sequence" question
	     05/22/2009 11:34
	     AM
* From the T10 Reflector (t10 at t10.org), posted by:
* "Knight, Frederick" <Frederick.Knight at netapp.com>
*
It is well understood that multiple concurrent overlapping commands can
interfere with each other.  For example, if I have 2 successful
concurrent SIMPLE tagged WRITE commands as follows:
1) WRITE 0s to LBA 1,2,3
2) WRITE 1s to LBA 1,2,3
There is no guarantee what will be in LBAs 1,2,3.  It could be 0s in
some of those LBAs, or 1s in some of those LBAs.  The device could
legally do the following:
WRITE 0s to LBA 1,3
WRITE 1s to LBA 1,3
seek to get to LBA 2 (maybe LBA 2 got revectored) WRITE 1s to LBA 2
WRITE 0s to LBA 2
So a READ of LBA 1,2,3 would not get all 0s or all 1s, it would get
whatever was the result of the interaction of those 2 overlapping WRITE
commands.  It is the responsibility of the application client to used
ORDERED commands or other means to create the consistency it needs.
Now, along comes ORWRITE, XDWRITE, XPWRITE, and other commands with an
"uninterruptable series of actions".
It seems clear that these "uninterruptable" actions can be ABORTed, so
in fact, some interruptions can occur.	I interpret the uninterruptable
nature to relate to the above case (multiple concurrent overlapping
commands that are also required to be uninterruptable).
So, change the above case to ORWRITEs (with an initial state of all
zeros in LBAs 1,2,3):
1) ORWRITE 1 into each LBA 1,2,3
2) ORWRITE 2 into each LBA 1,2,3
Because both commands are "uninterruptable" then I know, that when both
commmands complete, and I READ LBA 1,2,3 each LBA will contain 3 (1 and
2 will each be "OR"ed into each block).  I will not find the value 1 or
2 in any of those LBAs.  Because of the uninterruptable series of
actions, the result is as if the commands had been ORDERED commands.
So, next, what happens when I MIX overlapping concurrent uninterruptable
with interruptable commands?  Consider (again SIMPLE tagged, and an
initial state of all zeros in LBAs 1,2,3):
1) READ LBA 1,2,3 (transfer data for LBA 1,3)
2) ORWRITE 1 into each LBA 1,2,3
3) (transfer data for LBA 2 and complete READ command)
I assume since the READ is not required to be uninterruptable, it
operates just like the first case.  While the ORWRITE is executing, the
READ can continue to execute, so the READ could return some of those
LBAs with 0 in them, and some of those LBAs with 1 in them.
The consistency of an uninterrupted series of actions is only protected
/ guaranteed in relation to the actions of other overlapping
uninterrupted series of actions.
Is this generally agreed?  If not, this may become a July discussion
item.
	     Fred Knight
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From lohmeyer at t10.org  Sat May 23 23:00:55 2009
From: lohmeyer at t10.org (T10 Document Administrator)
Date: Sun, 24 May 2009 00:00:55 -0600
Subject: Recent T10 documents uploaded since 2009/05/17
Message-ID: <mailman.342.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* T10 Document Administrator <lohmeyer at t10.org>
*
Proposals
---------
SBC-3: GET LBA STATUS command
(by: David L. Black, Frederick Knight)
T10/08-341r3   Uploaded: 2009/05/20   48516 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=08-341r3.pdf
SBC-3 Thin Provisioning Threshold Notification
(by: Frederick Knight)
T10/09-011r4   Uploaded: 2009/05/19   182423 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-011r4.pdf
SSC-3 Resolve LB HPQ # 161 through 167
(by: Curtis Ballard)
T10/09-096r1   Uploaded: 2009/05/17   106037 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-096r1.pdf
Minutes: ADC-3 Minutes for May 4, 2009 Bellevue, WA
(by: Curtis Ballard)
T10/09-172r0   Uploaded: 2009/05/17   23815 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-172r0.pdf
Minutes of T10 Plenary Meeting #91 - May 7, 2009
(by: Weber & Lohmeyer)
T10/09-176r0   Uploaded: 2009/05/17   146133 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-176r0.htm
Minutes of T10 Plenary Meeting #91 - May 7, 2009
(by: Weber & Lohmeyer)
T10/09-176r0   Uploaded: 2009/05/17   353975 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-176r0.pdf
SAS-2.1 External MiniSAS HD Pinout
(by: Barry Olawsky)
T10/09-204r0   Uploaded: 2009/05/22   734974 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-204r0.pdf
External Mini-SAS HD Pinout Proposal
(by: Gourgen Oganessyan)
T10/09-206r0   Uploaded: 2009/05/21   52027 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-206r0.pdf
Minutes: CAP Thin Provisioning con-call May 20, 2009
(by: Frederick Knight)
T10/09-207r0   Uploaded: 2009/05/22   40519 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-207r0.pdf
Working Drafts
--------------
Object-Based Storage Devices - 2 (OSD-2)
(Editor: Ralph Weber)
 Rev: 05a      Uploaded: 2009/05/21   2455111 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=osd2r05a.pdf
Serial Attached SCSI - 2.1 (SAS-2.1)
(Editor: Alvin Cox)
 Rev: 02       Uploaded: 2009/05/19   4495800 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=sas21-r02.pdf
Serial Attached SCSI - 2.1 (SAS-2.1)
(Editor: Alvin Cox)
 Rev: 02       Uploaded: 2009/05/19   3269566 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=sas21-r02.zip
SCSI Primary Commands - 4 (SPC-4)
(Editor: Ralph Weber)
 Rev: 20       Uploaded: 2009/05/22   4885586 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=spc4r20.pdf
SAS Protocol Layer (SPL)
(Editor: George Penokie)
 Rev: 02       Uploaded: 2009/05/19   7810892 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=spl-r02.pdf
(Report generated on 2009/05/24 at 00:00:55)
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From roweber at IEEE.org  Mon May 25 19:59:15 2009
From: roweber at IEEE.org (Ralph Weber)
Date: Mon, 25 May 2009 21:59:15 -0500
Subject: SPC-4 r20a -- aka Tweak City
Message-ID: <mailman.343.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* Ralph Weber <roweber at ieee.org>
*
A one-off revision of SPC-4 has been uploaded as:
http://www.t10.org/cgi-bin/ac.pl?t=f&f=spc4r20a.pdf
R20a is *supposed* to be word-for-word identical to r20.
The new goodies in r20a are:
+ use of the currently preferred list capitalization
 (i.e., lower case, typically); and
+ a change of the base font to Arial.
The same techniques that have caught any number of
gaffes by the well-intentioned ANSI and ISO editors
were employed to check the SPC-4 editor's work. So,
finding mistakes should be at least challenging.
All the best,
.Ralph
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From keiji_katata at post.pioneer.co.jp  Tue May 26 03:11:04 2009
From: keiji_katata at post.pioneer.co.jp (keiji_katata at post.pioneer.co.jp)
Date: Tue, 26 May 2009 19:11:04 +0900
Subject: posted: Intel proposal and Lenovo proposal
Message-ID: <mailman.344.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* keiji_katata at post.pioneer.co.jp
*
Hello all,
I posted Intel proposal and Lenovo proposal for Item "9.1 Zero power
Proposal".
ftp.avc-pioneer.com/Mtfuji_7/Proposal/Jun09/
 Lenovo ODD SATA connector Optional use P4-0.2.ppt
 MtFujiOverview_5_21_09.pdf
 MtFujiProposal_05_21_09.pdf
Best regards,
Keiji Katata
PIONEER CORP.
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From roweber at IEEE.org  Wed May 27 08:27:06 2009
From: roweber at IEEE.org (Ralph Weber)
Date: Wed, 27 May 2009 10:27:06 -0500
Subject: REQUEST SENSE "previous versions" note
Message-ID: <mailman.345.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* Ralph Weber <roweber at ieee.org>
*
I have posted a proposal which hopefully reflects the
agreement reached in the May CAP working group regarding
the REQUEST SENSE DESC bit.
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-208r0.pdf
Although the CAP working group did not explicitly request
it, I have elected to avoid using any keywords (e.g., may)
in the proposed table footnote which, in effect, recommends
that Initiator implementors pay attention to the definition
of the DESC bit in SPC-3.
All the best,
.Ralph
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From lohmeyer at t10.org  Thu May 28 01:00:00 2009
From: lohmeyer at t10.org (T10 List Manager)
Date: Thu, 28 May 2009 02:00:00 -0600
Subject: T10 Reflector Monthly Reminder
Message-ID: <mailman.346.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* T10 List Manager <lohmeyer at t10.org>
*
This is an automatic monthly posting to the T10 Reflector.  If you
receive this message, it means that you are subscribed to the T10
Reflector email list.
The T10 Reflector is provided by the SCSI Trade Association and
maintained by LSI Corp. This reflector exists to discuss INCITS
T10 Technical Committee issues and to disseminate T10-related
information (minutes, meeting notices, etc.).
---------------------------------------------------------------------------
You do not need to be an INCITS T10 Technical Committee member to
use this reflector, however you must agree to:
 * read the INCITS Patent Policy and the INCITS Antitrust Guidelines
 * acknowledge that the activities of the T10 Technical Committee are
   governed by the INCITS policies and procedures as specified in the
   reference documents RD-1 and RD-2
 * acknowledge that draft documents may change at any time, without notice.
The INCITS Patent Policy, the INCITS Antitrust Guidelines, the RD-1, and
the RD-2 are all available on the www.incits.org web site.
If you do not agree to the above conditions, then you must unsubscribe
to this reflector.
---------------------------------------------------------------------------
T10 Reflector is not intended to carry commercial traffic. People who post
advertisements, job offers, etc. will be removed from the reflector.
Please visit http://www.t10.org/t10r.htm for instructions on subscribing,
unsubscribing, or searching the T10 Reflector archives.
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org


From kdbutt at us.ibm.com  Fri May 29 14:25:10 2009
From: kdbutt at us.ibm.com (Kevin D Butt)
Date: Fri, 29 May 2009 14:25:10 -0700
Subject: What is "registry" in Key Exchange payload?
Message-ID: <mailman.347.1441607349.22516.t10@sandbox.t10.org>

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

In SPC-4r20a, 7.6.3.5.3 Key Exchange payload
In the fifth paragraph <<The KEY EXCHANGE DATA field contains the sender?s 
Diffie-Hellman public value for this key exchange. The format of
key exchange data is as specified in the reference cited in that registry 
for the value used.>> it references a "registry".  To what registry is 
this referring?
I'm trying to figure out exactly what data gets passed between host and 
drive during this Diffie-Hellman step.	RFC 4306 pre-pends 8 bytes of 
header-type information, but don't know if that applies to the IKEv2-SCSI 
implementation as well (at least in this field).
Thanks,
Kevin D. Butt
SCSI & Fibre Channel Architect, Tape Firmware
MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744
Tel: 520-799-5280
Fax: 520-799-2723 (T/L:321)
Email address: kdbutt at us.ibm.com


From Mark.Evans at wdc.com  Fri May 29 15:56:08 2009
From: Mark.Evans at wdc.com (Mark Evans)
Date: Fri, 29 May 2009 15:56:08 -0700
Subject: SBC-3 r19 now available
Message-ID: <mailman.348.1441607349.22516.t10@sandbox.t10.org>

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

Hello,
The SCSI Block Commands - 3 (SBC-3) draft standard, revision 19, is now
available on T10.org.
Please feel free to call or send an email to me with any comments or
questions that you have about this stuff.
Regards,
Mark Evans
Western Digital Corporation


From Black_David at emc.com  Fri May 29 20:14:27 2009
From: Black_David at emc.com (Black_David at emc.com)
Date: Fri, 29 May 2009 23:14:27 -0400
Subject: What is "registry" in Key Exchange payload?
Message-ID: <mailman.349.1441607349.22516.t10@sandbox.t10.org>

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

Kevin,
You're looking for Table 448 in 7.6.3.6.5  (I have SPC-4r20, with
luck this didn't get renumbered in the 20a version).  The header info
is already specified in Table 423 in 7.6.3.5.3, so a second header is
not used.  Instead, go to either RFC 3526 or RFC 4753 from Table 448
in order to figure out how to represent the DH group value.
Thanks,
--David
________________________________
	From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of
Kevin D Butt
	Sent: Friday, May 29, 2009 5:25 PM
	To: t10 at t10.org; David L Swanson
	Subject: What is "registry" in Key Exchange payload?
	In SPC-4r20a, 7.6.3.5.3 Key Exchange payload 
	In the fifth paragraph <<The KEY EXCHANGE DATA field contains
the sender's Diffie-Hellman public value for this key exchange. The
format of 
	key exchange data is as specified in the reference cited in that
registry for the value used.>> it references a "registry".  To what
registry is this referring? 
	I'm trying to figure out exactly what data gets passed between
host and drive during this Diffie-Hellman step.  RFC 4306 pre-pends 8
bytes of header-type information, but don't know if that applies to the
IKEv2-SCSI implementation as well (at least in this field). 
	Thanks, 
	Kevin D. Butt
	SCSI & Fibre Channel Architect, Tape Firmware
	MS 6TYA, 9000 S. Rita Rd., Tucson, AZ 85744
	Tel: 520-799-5280
	Fax: 520-799-2723 (T/L:321)
	Email address: kdbutt at us.ibm.com
	http://www-03.ibm.com/servers/storage/
<http://www-03.ibm.com/servers/storage/&gt;  


From lohmeyer at t10.org  Sat May 30 23:00:55 2009
From: lohmeyer at t10.org (T10 Document Administrator)
Date: Sun, 31 May 2009 00:00:55 -0600
Subject: Recent T10 documents uploaded since 2009/05/24
Message-ID: <mailman.350.1441607349.22516.t10@sandbox.t10.org>

* From the T10 Reflector (t10 at t10.org), posted by:
* T10 Document Administrator <lohmeyer at t10.org>
*
Proposals
---------
SPL: Low Power Options for SAS phys
(by: George Penokie)
T10/09-063r3   Uploaded: 2009/05/27   812003 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-063r3.pdf
Minutes: ADC-3 Minutes for May 4, 2009 Bellevue, WA
(by: Curtis Ballard)
T10/09-172r1   Uploaded: 2009/05/26   23796 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-172r1.pdf
Agenda for T10 Meeting #92 July 2009
(by: John Lohmeyer)
T10/09-194r1   Uploaded: 2009/05/27   63200 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-194r1.pdf
SPC-3 vs SPC-4 Descriptor format REQUEST SENSE
(by: Ralph O. Weber)
T10/09-208r0   Uploaded: 2009/05/27   28772 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-208r0.pdf
OSD-3 Eliminate testing a non-existent capability
(by: Ralph O. Weber)
T10/09-209r0   Uploaded: 2009/05/27   28911 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-209r0.pdf
Proposal for SES-2 ISO editing fee
(by: Ralph O. Weber)
T10/09-210r0   Uploaded: 2009/05/27   25315 bytes
http://www.t10.org/cgi-bin/ac.pl?t=d&f=09-210r0.pdf
Working Drafts
--------------
Automation/Drive Interface Commands - 3 (ADC-3)
(Editor: Paul Stone)
 Rev: 01a      Uploaded: 2009/05/29   1067808 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=adc3r01a.pdf
SCSI Block Commands - 3 (SBC-3)
(Editor: Mark Evans)
 Rev: 19       Uploaded: 2009/05/29   1200967 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=sbc3r19.pdf
SCSI Primary Commands - 4 (SPC-4)
(Editor: Ralph Weber)
 Rev: 20a      Uploaded: 2009/05/25   4771664 bytes
http://www.t10.org/cgi-bin/ac.pl?t=f&f=spc4r20a.pdf
(Report generated on 2009/05/31 at 00:00:55)
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org