From folkert@vanheusden.com Mon Jan 24 05:27:31 2011 Return-Path: X-Original-To: ips@core3.amsl.com Delivered-To: ips@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 68DF33A6A86 for ; Mon, 24 Jan 2011 05:27:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qMmQnegb5Az5 for ; Mon, 24 Jan 2011 05:27:30 -0800 (PST) Received: from keetweej.vanheusden.com (tunnel947.ipv6.xs4all.nl [IPv6:2001:888:10:3b3::2]) by core3.amsl.com (Postfix) with ESMTP id 83FA23A68D5 for ; Mon, 24 Jan 2011 05:27:28 -0800 (PST) Received: from belle.intranet.vanheusden.com (belle.intranet.vanheusden.com [192.168.64.100]) by keetweej.vanheusden.com (Postfix) with ESMTP id B4DF216D43B for ; Mon, 24 Jan 2011 14:30:21 +0100 (CET) Received: by belle.intranet.vanheusden.com (Postfix, from userid 1000) id 8818C93366; Mon, 24 Jan 2011 14:30:21 +0100 (CET) Date: Mon, 24 Jan 2011 14:30:21 +0100 From: folkert To: ips@ietf.org Message-ID: <20110124133020.GN19602@belle.intranet.vanheusden.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: www.unixexpert.nl X-Chameleon-Return-To: folkert@vanheusden.com X-Xfmail-Return-To: folkert@vanheusden.com X-Phonenumber: +31-6-41278122 X-URL: http://www.vanheusden.com/ X-PGP-KeyID: 1F28D8AE X-GPG-fingerprint: AC89 09CE 41F2 00B4 FCF2 B174 3019 0E8C 1F28 D8AE X-Key: http://pgp.surfnet.nl:11371/pks/lookup?op=get&search=0x1F28D8AE Read-Receipt-To: Reply-By: Sat Jan 15 11:07:06 CET 2011 X-Message-Flag: www.unixexpert.nl User-Agent: Mutt/1.5.18 (2008-05-17) Subject: [Ips] this list X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2011 13:31:54 -0000 Hi, Is this list available for generic iSCSI questions? If so: some (linux iscsi target and window iStorageSErver) respond with valid data to Read Capacity(10) SCSI 0x25 command while for example nexenta store (an opensolaris system) responds with Check Condition. So I guess this is not the common way of determing the sector size and size of the device. Which command should I use for this? Thanks. Folkert van Heusden -- Nagios user? Check out CoffeeSaint - the versatile Nagios status viewer! http://www.vanheusden.com/java/CoffeeSaint/ ---------------------------------------------------------------------- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com From david.black@emc.com Mon Jan 24 07:36:55 2011 Return-Path: X-Original-To: ips@core3.amsl.com Delivered-To: ips@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B7513A68FA for ; Mon, 24 Jan 2011 07:36:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.599 X-Spam-Level: X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d8A+4LqeWn1X for ; Mon, 24 Jan 2011 07:36:54 -0800 (PST) Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id 8AF303A68E4 for ; Mon, 24 Jan 2011 07:36:54 -0800 (PST) Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p0OFdmo2009359 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Jan 2011 10:39:48 -0500 Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.226]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Mon, 24 Jan 2011 10:39:43 -0500 Received: from mxhub09.corp.emc.com (mxhub09.corp.emc.com [10.254.92.104]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p0OFd8pg023033; Mon, 24 Jan 2011 10:39:09 -0500 Received: from mx14a.corp.emc.com ([169.254.1.169]) by mxhub09.corp.emc.com ([10.254.92.104]) with mapi; Mon, 24 Jan 2011 10:39:08 -0500 From: To: , Date: Mon, 24 Jan 2011 10:39:05 -0500 Thread-Topic: [Ips] this list Thread-Index: Acu7y7k5xVmZlhFaQ02bNg5x7QrKLgAD8H/g Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E03D7689A49@MX14A.corp.emc.com> References: <20110124133020.GN19602@belle.intranet.vanheusden.com> In-Reply-To: <20110124133020.GN19602@belle.intranet.vanheusden.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-EMM-MHVC: 1 Subject: Re: [Ips] this list X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2011 15:36:55 -0000 That's actually more of a generic SCSI question than an iSCSI question, but= anyhow ... ... if READ CAPACITY (10) doesn't work, try READ CAPACITY (16) [opcode 0x9E= , service action 0x10]. OTOH, if READ CAPACITY (10) results in a Check Condition for invalid opcode= , the target that issued that CC does not comply with the SCSI standards, a= s support for READ CAPACITY (10) is mandatory for block devices in both the= SBC-2 standard and all drafts of the in-progress SBC-3 standard. Thanks, --David ---------------------------------------------------- David L. Black, Distinguished Engineer EMC Corporation, 176 South St., Hopkinton, MA=A0 01748 +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778= 6 david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754 ---------------------------------------------------- > -----Original Message----- > From: ips-bounces@ietf.org [mailto:ips-bounces@ietf.org] On Behalf Of fol= kert > Sent: Monday, January 24, 2011 8:30 AM > To: ips@ietf.org > Subject: [Ips] this list >=20 > Hi, >=20 > Is this list available for generic iSCSI questions? >=20 > If so: some (linux iscsi target and window iStorageSErver) respond with > valid data to Read Capacity(10) SCSI 0x25 command while for example > nexenta store (an opensolaris system) responds with Check Condition. > So I guess this is not the common way of determing the sector size and > size of the device. > Which command should I use for this? > Thanks. >=20 >=20 > Folkert van Heusden From Frederick.Knight@netapp.com Mon Jan 24 07:59:54 2011 Return-Path: X-Original-To: ips@core3.amsl.com Delivered-To: ips@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E4953A6ADF for ; Mon, 24 Jan 2011 07:59:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jQ7ZPcR9dKPF for ; Mon, 24 Jan 2011 07:59:53 -0800 (PST) Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id 604F13A6AFA for ; Mon, 24 Jan 2011 07:59:53 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.60,370,1291622400"; d="scan'208";a="509211107" Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 24 Jan 2011 08:02:47 -0800 Received: from sacrsexc2-prd.hq.netapp.com (sacrsexc2-prd.hq.netapp.com [10.99.115.28]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id p0OG2dkp024864; Mon, 24 Jan 2011 08:02:47 -0800 (PST) Received: from rtprsexc2-prd.hq.netapp.com ([10.100.161.115]) by sacrsexc2-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 24 Jan 2011 08:02:43 -0800 Received: from RTPMVEXC1-PRD.hq.netapp.com ([10.100.161.112]) by rtprsexc2-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 24 Jan 2011 11:02:39 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 24 Jan 2011 10:58:32 -0500 Message-ID: In-Reply-To: <20110124133020.GN19602@belle.intranet.vanheusden.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Ips] this list Thread-Index: Acu7y3xoWYuSaxqdS1C0PlnH8+LN8AAE5whw References: <20110124133020.GN19602@belle.intranet.vanheusden.com> From: "Knight, Frederick" To: "folkert" , X-OriginalArrivalTime: 24 Jan 2011 16:02:39.0750 (UTC) FILETIME=[20336A60:01CBBBE0] Subject: Re: [Ips] this list X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2011 15:59:54 -0000 The list t10@t10.org is good for generic SCSI questions like this. Basically, if it's a disk, you've got a device that is violating SCSI standards. That command is a mandatory (a command the device MUST support) for a block/disk device. If the device is not a disk, then different rules would apply. Fred Knight -----Original Message----- From: folkert [mailto:folkert@vanheusden.com]=20 Sent: Monday, January 24, 2011 8:30 AM To: ips@ietf.org Subject: [Ips] this list Hi, Is this list available for generic iSCSI questions? If so: some (linux iscsi target and window iStorageSErver) respond with valid data to Read Capacity(10) SCSI 0x25 command while for example nexenta store (an opensolaris system) responds with Check Condition. So I guess this is not the common way of determing the sector size and size of the device. Which command should I use for this? Thanks. Folkert van Heusden --=20 Nagios user? Check out CoffeeSaint - the versatile Nagios status viewer! http://www.vanheusden.com/java/CoffeeSaint/ ---------------------------------------------------------------------- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com _______________________________________________ Ips mailing list Ips@ietf.org https://www.ietf.org/mailman/listinfo/ips From Frederick.Knight@netapp.com Mon Jan 24 08:06:29 2011 Return-Path: X-Original-To: ips@core3.amsl.com Delivered-To: ips@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 803293A6905 for ; Mon, 24 Jan 2011 08:06:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PJOEGPnQJk9m for ; Mon, 24 Jan 2011 08:06:28 -0800 (PST) Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id 5A3733A68FE for ; Mon, 24 Jan 2011 08:06:28 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.60,370,1291622400"; d="scan'208";a="509214997" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 24 Jan 2011 08:09:21 -0800 Received: from sacrsexc1-prd.hq.netapp.com (sacrsexc1-prd.hq.netapp.com [10.99.115.27]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id p0OG9L5s017548; Mon, 24 Jan 2011 08:09:21 -0800 (PST) Received: from rtprsexc2-prd.hq.netapp.com ([10.100.161.115]) by sacrsexc1-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 24 Jan 2011 08:09:21 -0800 Received: from RTPMVEXC1-PRD.hq.netapp.com ([10.100.161.112]) by rtprsexc2-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 24 Jan 2011 11:09:20 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 24 Jan 2011 11:09:30 -0500 Message-ID: In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E03D7689A49@MX14A.corp.emc.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Ips] this list Thread-Index: Acu7y7k5xVmZlhFaQ02bNg5x7QrKLgAD8H/gAAFIdgA= References: <20110124133020.GN19602@belle.intranet.vanheusden.com> <7C4DFCE962635144B8FAE8CA11D0BF1E03D7689A49@MX14A.corp.emc.com> From: "Knight, Frederick" To: , , X-OriginalArrivalTime: 24 Jan 2011 16:09:20.0182 (UTC) FILETIME=[0EE07D60:01CBBBE1] Subject: Re: [Ips] this list X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2011 16:06:29 -0000 On the other hand, it depends on what CHECK CONDITION you are getting. Can you supply the full CDB and full response (all sense data including) = - status, sense key, ASC/ASCQ, data (if any). If you are sending a badly formed CDB, they the device is perfectly = within its rights to return CHECK CONDITION - but when it does, it = should also return more info about what is wrong (and that will be down = in the detailed bits of the returned sense data). Invalid OP Code is not valid for a disk to return (as per previous = comments), but INVALID FIELD IN CDB means you made a mistake. Fred Knight -----Original Message----- From: david.black@emc.com [mailto:david.black@emc.com]=20 Sent: Monday, January 24, 2011 10:39 AM To: folkert@vanheusden.com; ips@ietf.org Subject: Re: [Ips] this list That's actually more of a generic SCSI question than an iSCSI question, = but anyhow ... ... if READ CAPACITY (10) doesn't work, try READ CAPACITY (16) [opcode = 0x9E, service action 0x10]. OTOH, if READ CAPACITY (10) results in a Check Condition for invalid = opcode, the target that issued that CC does not comply with the SCSI = standards, as support for READ CAPACITY (10) is mandatory for block = devices in both the SBC-2 standard and all drafts of the in-progress = SBC-3 standard. Thanks, --David ---------------------------------------------------- David L. Black, Distinguished Engineer EMC Corporation, 176 South St., Hopkinton, MA=A0 01748 +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) = 293-7786 david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754 ---------------------------------------------------- > -----Original Message----- > From: ips-bounces@ietf.org [mailto:ips-bounces@ietf.org] On Behalf Of = folkert > Sent: Monday, January 24, 2011 8:30 AM > To: ips@ietf.org > Subject: [Ips] this list >=20 > Hi, >=20 > Is this list available for generic iSCSI questions? >=20 > If so: some (linux iscsi target and window iStorageSErver) respond = with > valid data to Read Capacity(10) SCSI 0x25 command while for example > nexenta store (an opensolaris system) responds with Check Condition. > So I guess this is not the common way of determing the sector size and > size of the device. > Which command should I use for this? > Thanks. >=20 >=20 > Folkert van Heusden _______________________________________________ Ips mailing list Ips@ietf.org https://www.ietf.org/mailman/listinfo/ips From folkert@vanheusden.com Mon Jan 24 08:24:22 2011 Return-Path: X-Original-To: ips@core3.amsl.com Delivered-To: ips@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B43EB3A690A for ; Mon, 24 Jan 2011 08:24:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_36=0.6] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VKEzF+l6figd for ; Mon, 24 Jan 2011 08:24:21 -0800 (PST) Received: from keetweej.vanheusden.com (tunnel947.ipv6.xs4all.nl [IPv6:2001:888:10:3b3::2]) by core3.amsl.com (Postfix) with ESMTP id 217613A6AE4 for ; Mon, 24 Jan 2011 08:24:19 -0800 (PST) Received: from belle.intranet.vanheusden.com (belle.intranet.vanheusden.com [192.168.64.100]) by keetweej.vanheusden.com (Postfix) with ESMTP id BC4CB16D4F0; Mon, 24 Jan 2011 17:27:09 +0100 (CET) Received: by belle.intranet.vanheusden.com (Postfix, from userid 1000) id 9905993365; Mon, 24 Jan 2011 17:27:09 +0100 (CET) Date: Mon, 24 Jan 2011 17:27:09 +0100 From: folkert To: "Knight, Frederick" Message-ID: <20110124162709.GS19602@belle.intranet.vanheusden.com> References: <20110124133020.GN19602@belle.intranet.vanheusden.com> <7C4DFCE962635144B8FAE8CA11D0BF1E03D7689A49@MX14A.corp.emc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Organization: www.unixexpert.nl X-Chameleon-Return-To: folkert@vanheusden.com X-Xfmail-Return-To: folkert@vanheusden.com X-Phonenumber: +31-6-41278122 X-URL: http://www.vanheusden.com/ X-PGP-KeyID: 1F28D8AE X-GPG-fingerprint: AC89 09CE 41F2 00B4 FCF2 B174 3019 0E8C 1F28 D8AE X-Key: http://pgp.surfnet.nl:11371/pks/lookup?op=get&search=0x1F28D8AE Read-Receipt-To: Reply-By: Sat Jan 15 11:07:06 CET 2011 X-Message-Flag: www.vanheusden.com User-Agent: Mutt/1.5.18 (2008-05-17) Cc: ips@ietf.org Subject: Re: [Ips] this list X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2011 16:24:22 -0000 Hi, The CDB I send is: SCSI CDB Read Capacity(10) [LUN: 0x0000] [Command Set:Direct Access Device (0x00) (Using default commandset)] [Response in: 12] Opcode: Read Capacity(10) (0x25) Logical Block Address: 0 PMI Flags: 0x00 .... ...0 = PMI: Pmi is CLEAR Vendor Unique = 0, NACA = 0, Link = 0 (0x25 for the first byte, the rest 0x00) the reply is: SCSI: SNS Info [LUN: 0x0000] Valid: 0 .111 0000 = SNS Error Type: Current Error (0x70) Filemark: 0, EOM: 0, ILI: 0 .... 0110 = Sense Key: Unit Attention (0x06) Sense Info: 0x00000000 Additional Sense Length: 10 Command-Specific Information: 00000000 Additional Sense Code+Qualifier: Power On, Reset, Or Bus Device Reset Occurred (0x2900) Field Replaceable Unit Code: 0x00 0... .... = SKSV: False Sense Key Specific: 000000 in hex: 70 00 06 00 00 00 00 0a 00 00 00 00 29 00 00 00 00 00 On Mon, Jan 24, 2011 at 11:09:30AM -0500, Knight, Frederick wrote: > On the other hand, it depends on what CHECK CONDITION you are getting. > > Can you supply the full CDB and full response (all sense data including) - status, sense key, ASC/ASCQ, data (if any). > > If you are sending a badly formed CDB, they the device is perfectly within its rights to return CHECK CONDITION - but when it does, it should also return more info about what is wrong (and that will be down in the detailed bits of the returned sense data). > > Invalid OP Code is not valid for a disk to return (as per previous comments), but INVALID FIELD IN CDB means you made a mistake. > > Fred Knight > > -----Original Message----- > From: david.black@emc.com [mailto:david.black@emc.com] > Sent: Monday, January 24, 2011 10:39 AM > To: folkert@vanheusden.com; ips@ietf.org > Subject: Re: [Ips] this list > > That's actually more of a generic SCSI question than an iSCSI question, but anyhow ... > > ... if READ CAPACITY (10) doesn't work, try READ CAPACITY (16) [opcode 0x9E, service action 0x10]. > > OTOH, if READ CAPACITY (10) results in a Check Condition for invalid opcode, the target that issued that CC does not comply with the SCSI standards, as support for READ CAPACITY (10) is mandatory for block devices in both the SBC-2 standard and all drafts of the in-progress SBC-3 standard. > > Thanks, > --David > ---------------------------------------------------- > David L. Black, Distinguished Engineer > EMC Corporation, 176 South St., Hopkinton, MA  01748 > +1 (508) 293-7953             FAX: +1 (508) 293-7786 > david.black@emc.com        Mobile: +1 (978) 394-7754 > ---------------------------------------------------- > > > -----Original Message----- > > From: ips-bounces@ietf.org [mailto:ips-bounces@ietf.org] On Behalf Of folkert > > Sent: Monday, January 24, 2011 8:30 AM > > To: ips@ietf.org > > Subject: [Ips] this list > > > > Hi, > > > > Is this list available for generic iSCSI questions? > > > > If so: some (linux iscsi target and window iStorageSErver) respond with > > valid data to Read Capacity(10) SCSI 0x25 command while for example > > nexenta store (an opensolaris system) responds with Check Condition. > > So I guess this is not the common way of determing the sector size and > > size of the device. > > Which command should I use for this? > > Thanks. > > > > > > Folkert van Heusden > _______________________________________________ > Ips mailing list > Ips@ietf.org > https://www.ietf.org/mailman/listinfo/ips Folkert van Heusden -- MultiTail ist eine flexible Applikation um Logfiles und Kommando Eingaben zu überprüfen. Inkl. Filter, Farben, Zusammenführen, Ansichten etc. http://www.vanheusden.com/multitail/ ---------------------------------------------------------------------- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com From roweber@ieee.org Mon Jan 24 09:10:05 2011 Return-Path: X-Original-To: ips@core3.amsl.com Delivered-To: ips@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8762728C0DB for ; Mon, 24 Jan 2011 09:10:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.999 X-Spam-Level: X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_36=0.6, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O3Vo4ss2kEcp for ; Mon, 24 Jan 2011 09:10:04 -0800 (PST) Received: from vms173013pub.verizon.net (vms173013pub.verizon.net [206.46.173.13]) by core3.amsl.com (Postfix) with ESMTP id 74A6F28C0D9 for ; Mon, 24 Jan 2011 09:10:04 -0800 (PST) Received: from [192.168.1.2] ([unknown] [71.170.237.40]) by vms173013.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LFJ002RTEH9QGE0@vms173013.mailsrvcs.net> for ips@ietf.org; Mon, 24 Jan 2011 11:12:45 -0600 (CST) Message-id: <4D3DB311.9080705@ieee.org> Date: Mon, 24 Jan 2011 11:12:49 -0600 From: Ralph Weber User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 MIME-version: 1.0 To: ips@ietf.org References: <20110124133020.GN19602@belle.intranet.vanheusden.com> <7C4DFCE962635144B8FAE8CA11D0BF1E03D7689A49@MX14A.corp.emc.com> <20110124162709.GS19602@belle.intranet.vanheusden.com> In-reply-to: <20110124162709.GS19602@belle.intranet.vanheusden.com> Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit Subject: Re: [Ips] this list X-BeenThere: ips@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IP Storage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2011 17:10:05 -0000 Not all CHECK CONDITIONs are created equal. When the Sense Key is Unit Attention, you are receiving the only flavor of asynchronous event notification that modern SCSI supports. If you retry the READ CAPACITY command, it should work. ON THE OTHER HAND You are well advised to pay heed to asynchronous event notifications such as the one shown below. They ALWAYS tell you something unusual has happened in the device. In this particular case, a power cycle (or equivalent, an iSCSI login perhaps) has happened since the last time you received status for some other SCSI command. If your driver's work queue has any outstanding commands that are waiting for status, that status will never come. If you previously used a MODE SELECT command to change the mode parameters, you might want to check to see if they are still in effect (frequently the changes will be gone). In a nutshell, all the saved state of the device is suspect. All the best, .Ralph On 1/24/2011 10:27 AM, folkert wrote: > Hi, > > The CDB I send is: > SCSI CDB Read Capacity(10) > [LUN: 0x0000] > [Command Set:Direct Access Device (0x00) (Using default commandset)] > [Response in: 12] > Opcode: Read Capacity(10) (0x25) > Logical Block Address: 0 > PMI Flags: 0x00 > .... ...0 = PMI: Pmi is CLEAR > Vendor Unique = 0, NACA = 0, Link = 0 > > (0x25 for the first byte, the rest 0x00) > > the reply is: > SCSI: SNS Info > [LUN: 0x0000] > Valid: 0 > .111 0000 = SNS Error Type: Current Error (0x70) > Filemark: 0, EOM: 0, ILI: 0 > .... 0110 = Sense Key: Unit Attention (0x06) > Sense Info: 0x00000000 > Additional Sense Length: 10 > Command-Specific Information: 00000000 > Additional Sense Code+Qualifier: Power On, Reset, Or Bus Device Reset Occurred (0x2900) > Field Replaceable Unit Code: 0x00 > 0... .... = SKSV: False > Sense Key Specific: 000000 > > in hex: > 70 00 06 00 00 00 00 0a 00 00 00 00 29 00 00 00 00 00 > > > On Mon, Jan 24, 2011 at 11:09:30AM -0500, Knight, Frederick wrote: >> On the other hand, it depends on what CHECK CONDITION you are getting. >> >> Can you supply the full CDB and full response (all sense data including) - status, sense key, ASC/ASCQ, data (if any). >> >> If you are sending a badly formed CDB, they the device is perfectly within its rights to return CHECK CONDITION - but when it does, it should also return more info about what is wrong (and that will be down in the detailed bits of the returned sense data). >> >> Invalid OP Code is not valid for a disk to return (as per previous comments), but INVALID FIELD IN CDB means you made a mistake. >> >> Fred Knight >> >> -----Original Message----- >> From: david.black@emc.com [mailto:david.black@emc.com] >> Sent: Monday, January 24, 2011 10:39 AM >> To: folkert@vanheusden.com; ips@ietf.org >> Subject: Re: [Ips] this list >> >> That's actually more of a generic SCSI question than an iSCSI question, but anyhow ... >> >> ... if READ CAPACITY (10) doesn't work, try READ CAPACITY (16) [opcode 0x9E, service action 0x10]. >> >> OTOH, if READ CAPACITY (10) results in a Check Condition for invalid opcode, the target that issued that CC does not comply with the SCSI standards, as support for READ CAPACITY (10) is mandatory for block devices in both the SBC-2 standard and all drafts of the in-progress SBC-3 standard. >> >> Thanks, >> --David >> ---------------------------------------------------- >> David L. Black, Distinguished Engineer >> EMC Corporation, 176 South St., Hopkinton, MA 01748 >> +1 (508) 293-7953 FAX: +1 (508) 293-7786 >> david.black@emc.com Mobile: +1 (978) 394-7754 >> ---------------------------------------------------- >> >>> -----Original Message----- >>> From: ips-bounces@ietf.org [mailto:ips-bounces@ietf.org] On Behalf Of folkert >>> Sent: Monday, January 24, 2011 8:30 AM >>> To: ips@ietf.org >>> Subject: [Ips] this list >>> >>> Hi, >>> >>> Is this list available for generic iSCSI questions? >>> >>> If so: some (linux iscsi target and window iStorageSErver) respond with >>> valid data to Read Capacity(10) SCSI 0x25 command while for example >>> nexenta store (an opensolaris system) responds with Check Condition. >>> So I guess this is not the common way of determing the sector size and >>> size of the device. >>> Which command should I use for this? >>> Thanks. >>> >>> >>> Folkert van Heusden >> _______________________________________________ >> Ips mailing list >> Ips@ietf.org >> https://www.ietf.org/mailman/listinfo/ips > > Folkert van Heusden >