From curtis.stevens at wdc.com Mon Oct 1 10:47:16 2012 From: curtis.stevens at wdc.com (Curtis Stevens) Date: Mon, 1 Oct 2012 17:47:16 +0000 Subject: SOPQI F2F Announcement Message-ID: Formatted message: HTML-formatted message Attachment #1: ann-sopqi_121010.pdf I have attached a PDF of the meeting announcement to this E-Mail. ------------------------------------------------- Curtis E. Stevens Director, Standards & Features Technology 3355 Michelson Dr. #100 Office: 1-1041 Irvine, Ca. 92612 Phone: 949-672-7933 Cell: 949-307-5050 E-Mail: Curtis.Stevens at WDC.com Remember, you may only be blamed for something if you are actually doing something. From alvin.cox at seagate.com Wed Oct 3 14:28:38 2012 From: alvin.cox at seagate.com (Alvin Cox) Date: Wed, 3 Oct 2012 16:28:38 -0500 Subject: Reminder: SAS PHY teleconference Thursday, October 4, 2012, 10:00 am CDT Message-ID: Formatted message: HTML-formatted message Mick Felton will chair in alvin's absence this week. Agenda: TBD Connector related Electrical SAS PHY meeting logistics: Applies to every Thursday, from Thursday, September 20, 2012 to Thursday, November 1, 2012 * except no teleconference September 27, 2012*. 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-3 Date: Every Thursday, from Thursday, September 20, 2012 to Thursday, November 1, 2012 Time: 10:00 am, Central Daylight Time (Chicago, GMT-05:00) Meeting Number: 827 988 093 Meeting Password: sas12gbps ------------------------------------------------------- To join the online meeting (Now from mobile devices!) ------------------------------------------------------- 1. Go to https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&R T=MiM3 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: sas12gbps 4. Click "Join". To view in other time zones or languages, please click the link: https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&O RT=MiM3 ------------------------------------------------------- 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=158650437&UID=0&ICS=MRS2&LD=1&RD=2 &ST=1&SHA2=pEI2tL0j5oE58s9ytOQWHuV98SACdVZgiFnrG-CNDds=&RT=MiM3 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 The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://seagate.webex.com/seagate/systemdiagnosis.php. 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, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation. -- Alvin Cox Seagate Technology, LLC Cell 405-206-4809 Office 405-392-3738 E-Mail alvin.cox at seagate.com From mickey.felton at emc.com Thu Oct 4 06:11:59 2012 From: mickey.felton at emc.com (Felton, Mickey) Date: Thu, 4 Oct 2012 09:11:59 -0400 Subject: Reminder: SAS PHY teleconference Thursday, October 4, 2012, 10:00 am CDT Message-ID: Formatted message: HTML-formatted message Does anyone have a topic for the meeting? I have no new updates. From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Alvin Cox Sent: Wednesday, October 03, 2012 5:29 PM To: T10 Reflector Subject: Reminder: SAS PHY teleconference Thursday, October 4, 2012, 10:00 am CDT Mick Felton will chair in alvin's absence this week. Agenda: TBD Connector related Electrical SAS PHY meeting logistics: Applies to every Thursday, from Thursday, September 20, 2012 to Thursday, November 1, 2012 except no teleconference September 27, 2012. 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-3 Date: Every Thursday, from Thursday, September 20, 2012 to Thursday, November 1, 2012 Time: 10:00 am, Central Daylight Time (Chicago, GMT-05:00) Meeting Number: 827 988 093 Meeting Password: sas12gbps ------------------------------------------------------- To join the online meeting (Now from mobile devices!) ------------------------------------------------------- 1. Go to https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&R T=MiM3 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: sas12gbps 4. Click "Join". To view in other time zones or languages, please click the link: https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&O RT=MiM3 ------------------------------------------------------- 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=158650437&UID=0&ICS=MRS2&LD=1&RD=2 &ST=1&SHA2=pEI2tL0j5oE58s9ytOQWHuV98SACdVZgiFnrG-CNDds=&RT=MiM3 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 The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://seagate.webex.com/seagate/systemdiagnosis.php. 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, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation. -- Alvin Cox Seagate Technology, LLC Cell 405-206-4809 Office 405-392-3738 E-Mail alvin.cox at seagate.com From lohmeyer at t10.org Sat Oct 6 23:01:22 2012 From: lohmeyer at t10.org (T10 Document Administrator) Date: Sun, 7 Oct 2012 00:01:22 -0600 Subject: Recent T10 documents uploaded since 2012/09/30 Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * T10 Document Administrator * Proposals --------- PQI Proposed Resolutions To Letter Ballot Comments On Section 4.3.2 (by: Stephen Finch) T10/12-387r2 Uploaded: 2012/10/03 125950 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-387r2.pdf Working Drafts -------------- (Report generated on 2012/10/07 at 00:01:22) * * 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 Mon Oct 8 11:37:14 2012 From: gerry.houlder at seagate.com (Gerry Houlder) Date: Mon, 8 Oct 2012 13:37:14 -0500 Subject: Question about use of IEEE COMPANY ID in 11-322r2 Message-ID: Formatted message: HTML-formatted message I have noted that 11-322r2 (Device crash dump) has a 32 bit field in the returned data for IEEE COMPANY ID. I'm sure this is because the SATA equivalent has a 4 byte field for this also. However, the IEEE Company ID is a 24 bit value. Neither the SATA version or the T10 version of the crash dump feature has any guideline about how the 24 bit value is aligned within the 32 bit field. There is also the issue of SATA being little endian and SCSI is big endian. This could lead to interpretation problems when comparing crash dump information from a SATA drive with crash dump information from a SCSI drive that are from the same manufacturer (and should have the same company ID value). I suggest that the 4 byte value should be changed to a 3 byte value plus a reserved byte. This would take care of how the 24 bit field is aligned. We should also discuss whether we need to require the bytes to be always little endian or always big endian regardless of whether the data is from a SATA or SCSI drive. From james.c.hatfield at seagate.com Mon Oct 8 12:09:47 2012 From: james.c.hatfield at seagate.com (James C Hatfield) Date: Mon, 8 Oct 2012 13:09:47 -0600 Subject: Question about use of IEEE COMPANY ID in 11-322r2 Message-ID: Formatted message: HTML-formatted message T13 has already defined (in ACS-3 rev 4: see A.23.2) that bits 31:24 are reserved bits 24:0 are the OUI Thank You !!! ----------------------------------------------------------------- Jim Hatfield Seagate Technology LLC e-mail: James.C.Hatfield at seagate.com s-mail: 389 Disc Drive; Longmont, CO 80503 USA voice: 720-684-2120 fax....: 720-684-2711 cell...: 720-771-8914 On Mon, Oct 8, 2012 at 12:37 PM, Gerry Houlder wrote: > I have noted that 11-322r2 (Device crash dump) has a 32 bit field in the > returned data for IEEE COMPANY ID. I'm sure this is because the SATA > equivalent has a 4 byte field for this also. However, the IEEE Company ID > is a 24 bit value. > > Neither the SATA version or the T10 version of the crash dump feature has > any guideline about how the 24 bit value is aligned within the 32 bit > field. There is also the issue of SATA being little endian and SCSI is big > endian. This could lead to interpretation problems when comparing crash > dump information from a SATA drive with crash dump information from a SCSI > drive that are from the same manufacturer (and should have the same company > ID value). > > I suggest that the 4 byte value should be changed to a 3 byte value plus a > reserved byte. This would take care of how the 24 bit field is aligned. We > should also discuss whether we need to require the bytes to be always > little endian or always big endian regardless of whether the data is from a > SATA or SCSI drive. > From curtis.stevens at wdc.com Tue Oct 9 15:13:38 2012 From: curtis.stevens at wdc.com (Curtis Stevens) Date: Tue, 9 Oct 2012 22:13:38 +0000 Subject: Question about use of IEEE COMPANY ID in 11-322r2 Message-ID: Formatted message: HTML-formatted message Are there any concerns about OUI-36? ------------------------------------------------- Curtis E. Stevens Director, Standards & Features Technology 3355 Michelson Dr. #100 Office: 1-1041 Irvine, Ca. 92612 Phone: 949-672-7933 Cell: 949-307-5050 E-Mail: Curtis.Stevens at WDC.com Remember, you may only be blamed for something if you are actually doing something. From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of James C Hatfield Sent: Monday, October 08, 2012 12:10 PM To: Gerry Houlder Cc: T10 Reflector Subject: Re: Question about use of IEEE COMPANY ID in 11-322r2 T13 has already defined (in ACS-3 rev 4: see A.23.2) that bits 31:24 are reserved bits 24:0 are the OUI Thank You !!! ----------------------------------------------------------------- Jim Hatfield Seagate Technology LLC e-mail: James.C.Hatfield at seagate.com s-mail: 389 Disc Drive; Longmont, CO 80503 USA voice: 720-684-2120 fax....: 720-684-2711 cell...: 720-771-8914 On Mon, Oct 8, 2012 at 12:37 PM, Gerry Houlder wrote: I have noted that 11-322r2 (Device crash dump) has a 32 bit field in the returned data for IEEE COMPANY ID. I'm sure this is because the SATA equivalent has a 4 byte field for this also. However, the IEEE Company ID is a 24 bit value. Neither the SATA version or the T10 version of the crash dump feature has any guideline about how the 24 bit value is aligned within the 32 bit field. There is also the issue of SATA being little endian and SCSI is big endian. This could lead to interpretation problems when comparing crash dump information from a SATA drive with crash dump information from a SCSI drive that are from the same manufacturer (and should have the same company ID value). I suggest that the 4 byte value should be changed to a 3 byte value plus a reserved byte. This would take care of how the 24 bit field is aligned. We should also discuss whether we need to require the bytes to be always little endian or always big endian regardless of whether the data is from a SATA or SCSI drive. From alvin.cox at seagate.com Wed Oct 10 13:56:11 2012 From: alvin.cox at seagate.com (Alvin Cox) Date: Wed, 10 Oct 2012 15:56:11 -0500 Subject: No PHY meeting this week, POWER DISABLE next week as the first topic. Message-ID: Formatted message: HTML-formatted message As per the discussion last week, there will be no pHY call this week. There will be discussion on the call next week regarding POWER DISABLE. I will post the meeting notice tomorrow with links to the POWER DISABLE proposals. -- Alvin Cox Seagate Technology, LLC Cell 405-206-4809 Office 405-392-3738 E-Mail alvin.cox at seagate.com From Frederick.Knight at netapp.com Thu Oct 11 08:46:56 2012 From: Frederick.Knight at netapp.com (Knight, Frederick) Date: Thu, 11 Oct 2012 15:46:56 +0000 Subject: Question about use of IEEE COMPANY ID in 11-322r2 Message-ID: Formatted message: HTML-formatted message I agree with Rob, we should more carefully specify this than we have some of our previous fields. SCSI (T10) already allows this so getting this right for the translation is important. Fred Knight From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Curtis Stevens Sent: Tuesday, October 09, 2012 6:14 PM To: James C Hatfield; Gerry Houlder Cc: T10 Reflector Subject: RE: Question about use of IEEE COMPANY ID in 11-322r2 Are there any concerns about OUI-36? ------------------------------------------------- Curtis E. Stevens Director, Standards & Features Technology 3355 Michelson Dr. #100 Office: 1-1041 Irvine, Ca. 92612 Phone: 949-672-7933 Cell: 949-307-5050 E-Mail: Curtis.Stevens at WDC.com Remember, you may only be blamed for something if you are actually doing something. From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of James C Hatfield Sent: Monday, October 08, 2012 12:10 PM To: Gerry Houlder Cc: T10 Reflector Subject: Re: Question about use of IEEE COMPANY ID in 11-322r2 T13 has already defined (in ACS-3 rev 4: see A.23.2) that bits 31:24 are reserved bits 24:0 are the OUI Thank You !!! ----------------------------------------------------------------- Jim Hatfield Seagate Technology LLC e-mail: James.C.Hatfield at seagate.com s-mail: 389 Disc Drive; Longmont, CO 80503 USA voice: 720-684-2120 fax....: 720-684-2711 cell...: 720-771-8914 On Mon, Oct 8, 2012 at 12:37 PM, Gerry Houlder wrote: I have noted that 11-322r2 (Device crash dump) has a 32 bit field in the returned data for IEEE COMPANY ID. I'm sure this is because the SATA equivalent has a 4 byte field for this also. However, the IEEE Company ID is a 24 bit value. Neither the SATA version or the T10 version of the crash dump feature has any guideline about how the 24 bit value is aligned within the 32 bit field. There is also the issue of SATA being little endian and SCSI is big endian. This could lead to interpretation problems when comparing crash dump information from a SATA drive with crash dump information from a SCSI drive that are from the same manufacturer (and should have the same company ID value). I suggest that the 4 byte value should be changed to a 3 byte value plus a reserved byte. This would take care of how the 24 bit field is aligned. We should also discuss whether we need to require the bytes to be always little endian or always big endian regardless of whether the data is from a SATA or SCSI drive. From clyon at scsita.org Thu Oct 11 13:04:48 2012 From: clyon at scsita.org (Chris Lyon) Date: Thu, 11 Oct 2012 13:04:48 -0700 Subject: [STA Members] Nov. T10 Meeting Hotel Reservation deadline is looming Message-ID: Formatted message: HTML-formatted message STA and T10 members, Just a reminder that this coming Monday is the deadline to book your room for the November T10 meetings in Tucson AZ. Loews Ventana Canyon is an incredible property and great place to meet so if you haven't why not take a minute and reserve your room now. Reservation information is below. Regards, Chris Loews Ventana Canyon 7000 North Resort Drive Tucson AZ 85750 Loews Reservations Center, 800-234-5117. From clyon at scsita.org Thu Oct 11 13:04:48 2012 From: clyon at scsita.org (Chris Lyon) Date: Thu, 11 Oct 2012 13:04:48 -0700 Subject: Nov. T10 Meeting Hotel Reservation deadline is looming Message-ID: Formatted message: HTML-formatted message STA and T10 members, Just a reminder that this coming Monday is the deadline to book your room for the November T10 meetings in Tucson AZ. Loews Ventana Canyon is an incredible property and great place to meet so if you haven't why not take a minute and reserve your room now. Reservation information is below. Regards, Chris Loews Ventana Canyon 7000 North Resort Drive Tucson AZ 85750 Loews Reservations Center, 800-234-5117. From kdbutt at us.ibm.com Thu Oct 11 14:06:50 2012 From: kdbutt at us.ibm.com (Kevin D Butt) Date: Thu, 11 Oct 2012 14:06:50 -0700 Subject: Nov. T10 Meeting Hotel Reservation deadline is looming Message-ID: Formatted message: HTML-formatted message Just a word of warning. If you miss getting reservations at this hotel, it is a long way to a hotel that isn't a plush resort and very expensive. Kevin D. Butt SCSI & Fibre Channel Architect, Tape Firmware Data Protection & Retention 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/ From: Chris Lyon To: "t10 at t10.org" , members at scsita.org, Date: 10/11/2012 01:52 PM Subject: Nov. T10 Meeting Hotel Reservation deadline is looming Sent by: owner-t10 at t10.org STA and T10 members, Just a reminder that this coming Monday is the deadline to book your room for the November T10 meetings in Tucson AZ. Loews Ventana Canyon is an incredible property and great place to meet so if you haven't why not take a minute and reserve your room now. Reservation information is below. Regards, Chris Loews Ventana Canyon 7000 North Resort Drive Tucson AZ 85750 Loews Reservations Center, 800-234-5117. From alvin.cox at seagate.com Fri Oct 12 09:01:32 2012 From: alvin.cox at seagate.com (Alvin Cox) Date: Fri, 12 Oct 2012 11:01:32 -0500 Subject: POWER DISABLE discussion scheduled for the October 18 SAS pHY teleconference Message-ID: Formatted message: HTML-formatted message Per the discussion during the September T10 plenary, the POWER DISABLE function now has a protocol proposal to provide system notification of the device supporting the feature. See the following proposals regarding the POWER DISABLE function. These proposals will be the first item on the 10/18/12 SAS PHY call. Call logistics are also provided below. 12-401r0 * From the T10 Reflector (t10 at t10.org), posted by: * T10 Document Administrator * Proposals --------- SBC-3: Sanitize operation definition clarification and expansion> (by: Mark Evans) T10/12-220r4 Uploaded: 2012/10/10 35236 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-220r4.pdf SBC-3: VERIFY SAME command (by: Frederick Knight) T10/12-246r3 Uploaded: 2012/10/12 235142 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-246r3.pdf SAT-3: VERIFY SAME Translation (by: Frederick Knight) T10/12-248r2 Uploaded: 2012/10/12 112016 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-248r2.pdf SPL-3: CDB length error fix (by: George Penokie) T10/12-347r1 Uploaded: 2012/10/09 70367 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-347r1.pdf SAS-3 addition of POWER DISABLE (by: Alvin Cox) T10/12-363r4 Uploaded: 2012/10/12 211966 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-363r4.pdf PQI Letter Ballot Comments Incorporated in PQI-R06 (by: Ie-Wei Njoo) T10/12-373r2 Uploaded: 2012/10/09 6345530 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-373r2.fdf PQI Letter Ballot Comments Incorporated in PQI-R06 (by: Ie-Wei Njoo) T10/12-373r2 Uploaded: 2012/10/09 85404 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-373r2.pdf PQI Letter Ballot Comments Incorporated in PQI-R06 (by: Ie-Wei Njoo) T10/12-373r2 Uploaded: 2012/10/09 945664 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-373r2.xls PQI Proposed Resolutions To Letter Ballot Comments On Section 4.3.2 (by: Stephen Finch) T10/12-387r3 Uploaded: 2012/10/10 180887 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-387r3.pdf PQI Proposed Resolutions To Letter Ballot Comments On Section 4.3.2 (by: Stephen Finch) T10/12-387r4 Uploaded: 2012/10/11 181148 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-387r4.pdf PQI - Common Interrupt Coalescing (by: Dave Landsman) T10/12-388r2 Uploaded: 2012/10/08 140474 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-388r2.pdf SBC-3 Erase operation for NVM (by: HengLiang Zhang) T10/12-400r0 Uploaded: 2012/10/12 31466 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-400r0.pdf SPL-3 Add reporting of POWER DISABLE signal support (by: Gerald Houlder) T10/12-401r0 Uploaded: 2012/10/09 47286 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-401r0.pdf SBC-4 Add reporting of unrecoverable errors that aren;t reassigned (by: Gerald Houlder) T10/12-402r0 Uploaded: 2012/10/09 77918 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-402r0.pdf SBC-3: Clarifications to POPULATE TOKEN and UNMAP length errors (by: Frederick Knight) T10/12-403r0 Uploaded: 2012/10/08 188740 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-403r0.pdf SPC-4: RSOC & RSTMF & PR interactions - late letter ballot comment (by: Frederick Knight) T10/12-404r0 Uploaded: 2012/10/08 170874 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-404r0.pdf SAM-5: UA and task set interaction claraification (by: Frederick Knight) T10/12-405r0 Uploaded: 2012/10/08 175917 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-405r0.pdf SBC-3: SPC4 LB comment HP-255 correction (by: Frederick Knight) T10/12-406r0 Uploaded: 2012/10/08 155381 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-406r0.pdf New SCSI Relationships figure for SOPQI (by: Curtis Stevens) T10/12-408r0 Uploaded: 2012/10/10 50738 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-408r0.docx New SCSI Relationships figure for SOPQI (by: Curtis Stevens) T10/12-408r0 Uploaded: 2012/10/10 82878 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-408r0.pdf New SCSI Relationships figure for SOPQI (by: Curtis Stevens) T10/12-408r0 Uploaded: 2012/10/10 40448 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-408r0.vsd New SCSI Relationships figure for SOPQI (by: Curtis Stevens) T10/12-408r1 Uploaded: 2012/10/10 82966 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-408r1.pdf New SCSI Relationships figure for SOPQI (by: Curtis Stevens) T10/12-408r2 Uploaded: 2012/10/10 83005 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-408r2.pdf T11 Liaison Report October 2012 (by: Steven Wilson) T10/12-409r0 Uploaded: 2012/10/10 25710 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-409r0.pdf Minutes of SAS PHY Working Group conference call October 4, 2012 (by: Mickey Felton) T10/12-410r0 Uploaded: 2012/10/10 169147 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-410r0.pdf Working Drafts -------------- PCIe(r) architecture Queuing Interface (PQI) (Editor: Ie-Wei Njoo) Rev: 06c Uploaded: 2012/10/09 1858715 bytes http://www.t10.org/cgi-bin/ac.pl?t=f&f=pqi-r06c.pdf (Report generated on 2012/10/14 at 00:01:21) * * 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 Mon Oct 15 08:04:46 2012 From: lohmeyer at t10.org (John Lohmeyer) Date: Mon, 15 Oct 2012 09:04:46 -0600 Subject: Make your November T10 week reservations TODAY Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * John Lohmeyer * Today is the deadline for making your room reservations at the November T10 meeting hotel in Tucson, AZ. If you haven't already done so, the announcement URL is: http://www.t10.org/ftp/t10/announce/ann-m112.pdf -- 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 kdbutt at us.ibm.com Mon Oct 15 16:47:18 2012 From: kdbutt at us.ibm.com (Kevin D Butt) Date: Mon, 15 Oct 2012 16:47:18 -0700 Subject: IBM's response to 12-405r0 SAM-5: UA and task set interaction claraification Message-ID: Formatted message: HTML-formatted message IBM has comments related to 12-405r0 SAM-5: UA and task set interaction claraification (by: Frederick Knight) T10/12-405r0 Uploaded: 2012/10/08 175917 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-405r0.pdf The current SCSI standard can be interpreted in multiple ways for UA 29/00. IBM would agree that clarification might be useful here providing we can agree on what that should be. However IBM does not think that clarification should be the current proposal in 12-405r0. Under this proposal if a lun has a UA 29/00 pending, multiple tasks would be allowed to be accepted by that lun. The first task processed (enabled) would fail with UA 29/00. The subsequent ones would be governed by QErr bit settings. This seems problematic for a number of situations where a device's state may have substantially changed thus compromising data from the initiator perspective. Thus the subsequent tasks may be processed from a device that is in a questionable state (i.e. loss of reservations and thus no synchronization of read/writes with other hosts, difference in mode settings etc). A way to avoid the above issue would be to have the device support QErr = x1 settings. This though is problematic, since a device may not support this setting. A more robust solution (from the initiator's perspective) is for the first command to be failed immediately with UA 29/00 before other commands are accepted. The subsequent commands would then be governed by whether the faulted command had the NACA=1 bit set. If so then subsequent commands would be failed with ACA ACTIVE status. This is how some of IBM's engineers interpret the standard. Based on how SCSI evolved, IBM thinks that this is more consistent with the original intent of the standard. Thanks, Kevin D. Butt SCSI & Fibre Channel Architect, Tape Firmware Data Protection & Retention 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 roweber at ieee.org Tue Oct 16 18:34:55 2012 From: roweber at ieee.org (Ralph Weber) Date: Tue, 16 Oct 2012 20:34:55 -0500 Subject: Latest LUN Conglomeration proposal uploaded Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * Ralph Weber * The newest revision of the LUN Conglomeration proposal for SAM-5 has been uploaded. http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-247r3.pdf The early availability of this document is intended to allow the myriad of interested parties plenty of time to contemplate its elegant nuances (or, if you prefer, stupid mistakes). Owing to the lack of progress thus far on the SPC-4 Letter Ballot no guarantees can be provided regarding the disposition of comments received prior to the T10 meeting week in Tucson. This warning is not intended to discourage comments as much as it desires to honestly calibrate expectations. 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 roweber at ieee.org Wed Oct 17 07:09:39 2012 From: roweber at ieee.org (Ralph Weber) Date: Wed, 17 Oct 2012 09:09:39 -0500 Subject: "Small" tweak in LUN Conglomeration proposal Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * Ralph Weber * It was brought to my attention that subsidiary logical units cannot be well-known logical units, a fact which 12-247r3 omitted. Another concern is that neither administrative nor subsidiary logical units can be dependent logical units. Among other things, the LUN format requirements conflict if this is allowed. A new revision has been uploaded to include these facts. http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-247r4.pdf 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 alvin.cox at seagate.com Wed Oct 17 08:52:21 2012 From: alvin.cox at seagate.com (Alvin Cox) Date: Wed, 17 Oct 2012 10:52:21 -0500 Subject: Reminder: SAS PHY teleconference Thursday, October 18, 2012, 10:00 am CDT Message-ID: Formatted message: HTML-formatted message Agenda: Per the discussion during the September T10 plenary, the POWER DISABLE function now has a protocol proposal to provide system notification of the device supporting the feature. See the following proposals regarding the POWER DISABLE function. These proposals will be the first item on the 10/18/12 SAS PHY call. Call logistics are also provided below. 12-401r0 * From the T10 Reflector (t10 at t10.org), posted by: * Radhakrishnan Jagannathan * ----- Original Message ----- From: "Tim Symons" To: "Radhakrishnan Jagannathan" Sent: Thursday, October 18, 2012 5:07:40 PM Subject: RE: SOP/PQI Letter Ballot Hi Tim, Thanks for your response. I didn't get any other reply to this request. I can talk to our architecture team in my company and come out with a proposal. Mean while, please let me know if there are any proceeds in this regards. Thanks and Regards, Jagan Jagan, I???m not sure if anyone has answered your enquiry but here is my recommendation. There are currently no rules that limit the usage and extent of the bit-bucket operation, so it is possible to create the condition that you described. There has been some discussions on bounding the bit-bucket usage to sensible usage models, but there are many cases, and so a comprehensive proposal would be required to define: 1. conditions that are allowed 2. conditions that are not allowed 3. error states or reporting mechanism for the case where a disallowed condition occurs It???s the definitions and error scope that requires detailed analysis to ensure that conditions are adhered to, or exceptions are appropriately flagged to the system as an error for corrective action without data loss. Would you be willing to make such a proposal to the group? Regards Tim. Tim Symons Principal Engineer PMC-Sierra Ltd. 8555 Baxter Place Burnaby, BC, V5A4V7 Canada Cell: 778 998 5025 E-mail Tim.Symons at pmcs.com From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Radhakrishnan Jagannathan Sent: Monday, September 17, 2012 2:21 PM To: t10 at t10.org Cc: 'Radhakrishnan Jagannathan' Subject: SOP/PQI Letter Ballot Hello, I have a general question about SGK bit bucket descriptor. I understand that, based on the standard, bit bucket descriptor can be placed in the last segment descriptor. Having said that, will there be a possibility for the PQI Host driver to send every single entry in the last segment descriptor as bit bucket entries? If not, can we explicitly say that in SOP IUs, the last segment descriptor will not contain bit bucket descriptor(s)? This is mainly to ease the H/W implementation of PQI compliant device. Thanks, Jagan * * 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 Oct 20 23:01:32 2012 From: lohmeyer at t10.org (T10 Document Administrator) Date: Sun, 21 Oct 2012 00:01:32 -0600 Subject: Recent T10 documents uploaded since 2012/10/14 Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * T10 Document Administrator * Proposals --------- Logical Unit Groups (aka Conglomerates) in SAM-5 and SPC-5 (by: Ralph Weber) T10/12-247r3 Uploaded: 2012/10/16 106123 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-247r3.pdf Logical Unit Groups (aka Conglomerates) in SAM-5 and SPC-5 (by: Ralph Weber) T10/12-247r4 Uploaded: 2012/10/17 108305 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-247r4.pdf SBC-3 Allow verify operations on unmapped LBAs (by: Rob Elliott) T10/12-282r3 Uploaded: 2012/10/18 351814 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-282r3.pdf SBC-3 REASSIGN BLOCKS simplifications for logical block provisioning (by: Rob Elliott) T10/12-283r2 Uploaded: 2012/10/18 519234 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-283r2.pdf PQI - Common Interrupt Coalescing (by: Dave Landsman) T10/12-388r3 Uploaded: 2012/10/19 146317 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-388r3.pdf Agenda for T10 Meeting #112 November 8, 2012 (by: John Lohmeyer) T10/12-392r1 Uploaded: 2012/10/16 15280 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-392r1.pdf SBC-3 Garbage collection for NVM HD (by: HengLiang Zhang) T10/12-411r0 Uploaded: 2012/10/17 30829 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-411r0.pdf Working Drafts -------------- SCSI Architecture Model - 5 (SAM-5) (Editor: George Penokie) Rev: 12 Uploaded: 2012/10/18 1504452 bytes http://www.t10.org/cgi-bin/ac.pl?t=f&f=sam5r12.pdf Serial Attached SCSI - 3 (SAS-3) (Editor: Alvin Cox) Rev: 03 Uploaded: 2012/10/18 3207974 bytes http://www.t10.org/cgi-bin/ac.pl?t=f&f=sas3r03.pdf Serial Attached SCSI - 3 (SAS-3) (Editor: Alvin Cox) Rev: 03 Uploaded: 2012/10/18 3595391 bytes http://www.t10.org/cgi-bin/ac.pl?t=f&f=sas3r03.zip (Report generated on 2012/10/21 at 00:01:32) * * 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 Wed Oct 24 12:21:22 2012 From: alvin.cox at seagate.com (Alvin Cox) Date: Wed, 24 Oct 2012 14:21:22 -0500 Subject: Reminder: SAS PHY teleconference Thursday, October 25, 2012, 10:00 am CDT Message-ID: Formatted message: HTML-formatted message Agenda: Continued discussion of the POWER DISABLE proposal 12-401r0 Formatted message: HTML-formatted message Attachment #1: image001.gif Tim, In the meeting announcement (http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-421r0.pdf), is the hotel rate quoted in Canadian or US dollars? At the moment they're very close to par, but that could change. Thanks, Paul _____________________________________________________________________________ ________________________ Paul A. Suhler, PhD | Firmware Engineer | Quantum Corporation | Office: 949.856.7748 | paul.suhler at quantum.com [be-certain_lockup.gif] * From the T10 Reflector (t10 at t10.org), posted by: * "Tim Symons" * Rates quoted are Canadian Dollars. Today's exchange rate is around parity, but when we made the meeting reservation it was (and normally is) in favour of the US dollar. Tim. From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Paul Suhler Sent: Thursday, October 25, 2012 11:04 AM To: T10 E-mail Reflector Subject: March 2013 Hotel Currency Tim, In the meeting announcement (http://www.t10.org/cgi-bin/ac.pl?t=3Dd&f=3D12-421r0.pdf), is the hotel rate quoted in Canadian or US dollars? At the moment they're very close to par, but that could change. Thanks, Paul ________________________________________________________________________ _____________________________ Paul A. Suhler, PhD | Firmware Engineer | Quantum Corporation | Office: 949.856.7748 | paul.suhler at quantum.com * From the T10 Reflector (t10 at t10.org), posted by: * T10 Document Administrator * Proposals --------- SBC-3: Definitions for read, write, verify, and unmap operations (by: Mark Evans) T10/12-139r4 Uploaded: 2012/10/24 189165 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-139r4.pdf SPL-3 Persistent Connection (by: George Penokie) T10/12-251r5 Uploaded: 2012/10/23 614228 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-251r5.pdf SPL-3:Management ECM/Application Client connection close request (by: George Penokie) T10/12-380r1 Uploaded: 2012/10/24 416547 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-380r1.pdf PQI - Common Interrupt Coalescing (by: Dave Landsman) T10/12-388r4 Uploaded: 2012/10/23 149096 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-388r4.pdf Results of Letter Ballot on forwarding SAT-3 to First Public Review (by: John Lohmeyer) T10/12-391r0 Uploaded: 2012/10/25 264537 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-391r0.pdf Results of Letter Ballot on forwarding SAT-3 to First Public Review (by: John Lohmeyer) T10/12-391r0 Uploaded: 2012/10/25 472301 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-391r0.txt Minutes of SAS PHY Working Group conference call October 18, 2012 (by: Alvin Cox) T10/12-413r0 Uploaded: 2012/10/25 25323 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-413r0.pdf SBC-4 Simplified SCSI - base and maintenance feature sets (by: Rob Elliott, Kevin Marks, Dave Minturn, Calvin Chen) T10/12-414r0 Uploaded: 2012/10/23 273619 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-414r0.pdf SPC-4: Add Not Ready ASCs for Subsidiary Logical Units (by: David Black) T10/12-415r0 Uploaded: 2012/10/22 18644 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-415r0.pdf Add Not Ready ASCs for Subsidiary Logical Units (by: David Black, Murali Rajagopal) T10/12-415r1 Uploaded: 2012/10/23 18828 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-415r1.pdf Systematic Review of ISO/IEC 14776-326:2002 (RBC) (by: Rachel Porter) T10/12-416r0 Uploaded: 2012/10/23 58412 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-416r0.htm Systematic Review of ISO/IEC 14776-326:2002 (RBC) (by: Rachel Porter) T10/12-416r0 Uploaded: 2012/10/23 41290 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-416r0.pdf SBC-3 Model Logical Unit operations as classes (by: Rob Elliott) T10/12-417r0 Uploaded: 2012/10/23 125278 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-417r0.pdf SBC-3 Model Logical Unit operations as classes (by: Rob Elliott) T10/12-417r1 Uploaded: 2012/10/25 125412 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-417r1.pdf March 2013 Vancouver Meeting Announcement (by: Tim Symons) T10/12-418r0 Uploaded: 2012/10/23 42914 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-418r0.pdf SPL-2: Inside ZPSDS persistent = 0 is broken (by: George Penokie) T10/12-419r0 Uploaded: 2012/10/24 376115 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-419r0.pdf SBC-3 Clearing pseudo unrecovered errors (by: Rob Elliott) T10/12-420r0 Uploaded: 2012/10/24 120457 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-420r0.pdf Meeting Announcement: T10 Week Mar 11-15, 2013 -- Vancouver, BC (by: Tim Symons) T10/12-421r0 Uploaded: 2012/10/24 42914 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-421r0.pdf Minutes of SAS PHY Working Group conference call October 25, 2012 (by: Alvin Cox) T10/12-423r0 Uploaded: 2012/10/25 29924 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-423r0.pdf SAS-3 POWER DISABLE activation level (by: Alvin Cox) T10/12-424r0 Uploaded: 2012/10/25 36939 bytes http://www.t10.org/cgi-bin/ac.pl?t=d&f=12-424r0.pdf Working Drafts -------------- (Report generated on 2012/10/28 at 00:01:22) * * 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 Oct 28 01:00:00 2012 From: lohmeyer at t10.org (T10 List Manager) Date: Sun, 28 Oct 2012 02:00:00 -0600 Subject: T10 Reflector Monthly Reminder Message-ID: * From the T10 Reflector (t10 at t10.org), posted by: * T10 List Manager * 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 alvin.cox at seagate.com Wed Oct 31 12:12:24 2012 From: alvin.cox at seagate.com (Alvin Cox) Date: Wed, 31 Oct 2012 14:12:24 -0500 Subject: Reminder: SAS PHY teleconference Thursday, November 1, 2012, 10:00 am CDT Message-ID: Formatted message: HTML-formatted message Agenda: Connector related Molex proposal regarding 12G passive cables Electrical SAS PHY meeting logistics: Applies to every Thursday, from Thursday, September 20, 2012 to Thursday, November 1, 2012 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-3 Date: Every Thursday, from Thursday, September 20, 2012 to Thursday, November 1, 2012 Time: 10:00 am, Central Daylight Time (Chicago, GMT-05:00) Meeting Number: 827 988 093 Meeting Password: sas12gbps ------------------------------------------------------- To join the online meeting (Now from mobile devices!) ------------------------------------------------------- 1. Go to https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&R T=MiM3 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: sas12gbps 4. Click "Join". To view in other time zones or languages, please click the link: https://seagate.webex.com/seagate/j.php?ED=158650437&UID=0&PW=NODQzMjNhYTdm&O RT=MiM3 ------------------------------------------------------- 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=158650437&UID=0&ICS=MRS2&LD=1&RD=2 &ST=1&SHA2=pEI2tL0j5oE58s9ytOQWHuV98SACdVZgiFnrG-CNDds=&RT=MiM3 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 The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://seagate.webex.com/seagate/systemdiagnosis.php. 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, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation.