Re: [Ips] this list

<david.black@emc.com> Mon, 24 January 2011 15:36 UTC

Return-Path: <david.black@emc.com>
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 <ips@core3.amsl.com>; 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 <ips@core3.amsl.com>; 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 <ips@ietf.org>; 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: david.black@emc.com
To: folkert@vanheusden.com, ips@ietf.org
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 <ips.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ips>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=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, 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