From owner-freebsd-scsi@FreeBSD.ORG Mon Oct 7 11:06:52 2013 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4A1728C0 for ; Mon, 7 Oct 2013 11:06:52 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 37E302844 for ; Mon, 7 Oct 2013 11:06:52 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r97B6qwo077845 for ; Mon, 7 Oct 2013 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r97B6pl3077843 for freebsd-scsi@FreeBSD.org; Mon, 7 Oct 2013 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 7 Oct 2013 11:06:51 GMT Message-Id: <201310071106.r97B6pl3077843@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 11:06:52 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/179932 scsi [ciss] ciss i/o stall problem with HP Bl Gen8 (and HP o kern/178795 scsi [mps] MSI for mps driver doesn't work under vmware o kern/165982 scsi [mpt] mpt instability, drive resets, and losses on Fre o kern/165740 scsi [cam] SCSI code must drain callbacks before free f kern/162256 scsi [mpt] QUEUE FULL EVENT and 'mpt_cam_event: 0x0' o docs/151336 scsi Missing documentation of scsi_ and ata_ functions in c o kern/148083 scsi [aac] Strange device reporting o kern/144648 scsi [aac] Strange values of speed and bus width in dmesg o kern/142351 scsi [mpt] LSILogic driver performance problems o kern/134488 scsi [mpt] MPT SCSI driver probes max. 8 LUNs per device o kern/130621 scsi [mpt] tranfer rate is inscrutable slow when use lsi213 f kern/129602 scsi [ahd] ahd(4) gets confused and wedges SCSI bus f kern/123674 scsi [ahc] ahc driver dumping o sparc/121676 scsi [iscsi] iscontrol do not connect iscsi-target on sparc 14 problems total. From owner-freebsd-scsi@FreeBSD.ORG Wed Oct 9 12:20:43 2013 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A9949874 for ; Wed, 9 Oct 2013 12:20:43 +0000 (UTC) (envelope-from bjwela@gmail.com) Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1E1A62251 for ; Wed, 9 Oct 2013 12:20:42 +0000 (UTC) Received: by mail-la0-f48.google.com with SMTP id er20so593457lab.7 for ; Wed, 09 Oct 2013 05:20:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type :thread-index:content-language; bh=vi2oVlvabH52cyF3qDm5IZIm8J6HttOppp2UxMZF8Xs=; b=wOXQ6q/2CTNvzku0UG6czKkvF2AbjbPIhq5+S2rBafbFxPyJ6EPsGXWg4640Hc2DZQ VPNm5WOD6v2uTpL4Xcts85ucMkAcKeXoJBDvHNhVZ1T5CschhCob2FmbgKdYkUZWZWqU QIBllwQQISs2XWoaDdcPnj4KePI4wOv8vvzIbrv6M9alQ84cbW4AgyRqcjEEkZ5ELl+9 nIbrljvJcbfyjCC0r0TUufsYclep3XyU4rRpr2Wuwdt0Ogo1sxjCtpBuFi8khG+td6BH DzllIue6v0LtuU8kFeomgwSIZ8169cgx1u1WKDNoz6xMynptGc/kdMQ73swMK8er7tgI ElWw== X-Received: by 10.152.115.242 with SMTP id jr18mr1316780lab.40.1381321241011; Wed, 09 Oct 2013 05:20:41 -0700 (PDT) Received: from bjornxps12 (5.35.185.180.c.fiberdirekt.net. [5.35.185.180]) by mx.google.com with ESMTPSA id ap7sm35034808lac.10.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 09 Oct 2013 05:20:39 -0700 (PDT) From: =?iso-8859-1?Q?Bj=F6rn_Larsson?= To: Subject: camcontrol cmd -c - for listing EVPD 0x83 Date: Wed, 9 Oct 2013 14:20:34 +0200 Message-ID: <002701cec4e9$f5078d60$df16a820$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: Ac7E5zTDaqqDtAD3Sem+murzxBr9lQ== Content-Language: sv Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 12:20:43 -0000 Dear All,=20 =20 I am trying to use =93camcontrol cmd =96c=94 to send a scsi inquiry = command that lists 0x83 (device identification) data instead of the standard output = given by the =93camcontrol inquiry=94 but I cannot get it to work properly. = This could be due to that I am not understanding the hex format, so hopefully = someone out there can point me in the right direction? The only information I am looking for is the WWN identifier of the SAS target. =20 =20 I have tried to create a SCSI CDB command according the information on: http://en.wikipedia.org/wiki/SCSI_Inquiry_Command and come up with the following command:=20 =20 # camcontrol cmd da0 =96c 0x009600830112 =96i 96 =96 =20 12 is inquiry 01 EVPD bit is set 83 VPD Page 00 MSB length 96 LSB length 00 reserved =20 =20 The problem is that I cannot get any output from the command? Am I using = it wrong?=20 =20 Thanks,=20 =20 Bj=F6rn =20 =20 =20 =20 =20 From owner-freebsd-scsi@FreeBSD.ORG Wed Oct 9 15:32:19 2013 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 00E0048C for ; Wed, 9 Oct 2013 15:32:18 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [128.127.144.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 512D02F3A for ; Wed, 9 Oct 2013 15:32:17 +0000 (UTC) Received: from [192.168.248.33] ([192.168.248.33]) by elf.hq.norma.perm.ru (8.14.5/8.14.5) with ESMTP id r99F7q52022037 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 9 Oct 2013 21:07:52 +0600 (YEKT) (envelope-from emz@norma.perm.ru) Message-ID: <52557144.9070408@norma.perm.ru> Date: Wed, 09 Oct 2013 21:07:48 +0600 From: "Eugene M. Zheganin" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: qlogic 2600 hbas Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (elf.hq.norma.perm.ru [192.168.3.10]); Wed, 09 Oct 2013 21:07:52 +0600 (YEKT) X-Spam-Status: No hits=-101.0 bayes=0.5 testhits ALL_TRUSTED=-1, USER_IN_WHITELIST=-100 autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on elf.hq.norma.perm.ru X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 15:32:19 -0000 Hi. Are there any plans to add the support for newer 16Gb Qlogic adapters ? Thanks. Eugene. From owner-freebsd-scsi@FreeBSD.ORG Wed Oct 9 15:48:41 2013 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 47DB5900 for ; Wed, 9 Oct 2013 15:48:41 +0000 (UTC) (envelope-from mj@feral.com) Received: from virtual.feral.com (virtual.feral.com [216.224.170.83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0EEDB2058 for ; Wed, 9 Oct 2013 15:48:40 +0000 (UTC) Received: from nicasio.dssd.com (50-76-39-249-ip-static.hfc.comcastbusiness.net [50.76.39.249]) by virtual.feral.com (8.14.4/8.14.4) with ESMTP id r99FlXDD025718 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 9 Oct 2013 08:47:34 -0700 Message-ID: <52557A95.9030607@feral.com> Date: Wed, 09 Oct 2013 08:47:33 -0700 From: Matthew Jacob User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Re: qlogic 2600 hbas References: <52557144.9070408@norma.perm.ru> In-Reply-To: <52557144.9070408@norma.perm.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (virtual.feral.com [216.224.170.83]); Wed, 09 Oct 2013 08:47:34 -0700 (PDT) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 15:48:41 -0000 On 10/9/13 8:07 AM, Eugene M. Zheganin wrote: > Hi. > > Are there any plans to add the support for newer 16Gb Qlogic adapters ? > > Thanks. > Eugene. > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" This came up recently for the CNA series. I don't have the h/w and was somewhat ambivalent about doing the work. I'm less ambivalent now. If somebody loans me the boards, I will do the work. From owner-freebsd-scsi@FreeBSD.ORG Wed Oct 9 15:57:39 2013 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 09B11C65 for ; Wed, 9 Oct 2013 15:57:39 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CE84720F0 for ; Wed, 9 Oct 2013 15:57:38 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id r99FvVZq046527; Wed, 9 Oct 2013 09:57:31 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id r99FvVwM046526; Wed, 9 Oct 2013 09:57:31 -0600 (MDT) (envelope-from ken) Date: Wed, 9 Oct 2013 09:57:31 -0600 From: "Kenneth D. Merry" To: Bj?rn Larsson Subject: Re: camcontrol cmd -c - for listing EVPD 0x83 Message-ID: <20131009155731.GA43480@nargothrond.kdm.org> References: <002701cec4e9$f5078d60$df16a820$@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002701cec4e9$f5078d60$df16a820$@gmail.com> User-Agent: Mutt/1.4.2i Cc: freebsd-scsi@freebsd.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 15:57:39 -0000 On Wed, Oct 09, 2013 at 14:20:34 +0200, Bj?rn Larsson wrote: > Dear All, > > > > I am trying to use ?camcontrol cmd ?c? to send a scsi inquiry command that > lists 0x83 (device identification) data instead of the standard output given > by the ?camcontrol inquiry? but I cannot get it to work properly. This could > be due to that I am not understanding the hex format, so hopefully someone > out there can point me in the right direction? The only information I am > looking for is the WWN identifier of the SAS target. > > > > I have tried to create a SCSI CDB command according the information on: > > http://en.wikipedia.org/wiki/SCSI_Inquiry_Command and come up with the > following command: > > > > # camcontrol cmd da0 ?c 0x009600830112 ?i 96 ? > > > > 12 is inquiry > > 01 EVPD bit is set > > 83 VPD Page > > 00 MSB length > > 96 LSB length > > 00 reserved The command isn't one hexadecimal number, but rather individual hexadecimal numbers for each byte in the CDB. You also need to specify either "-" to direct the output to stdout, or specify the output format. For example: # camcontrol cmd da16 -v -c "12 1 83 0 ff 0" -i 0xff - |hd 00000000 00 83 00 48 01 03 00 08 50 00 c5 00 10 3f 70 23 |...H....P....?p#| 00000010 61 93 00 08 50 00 c5 00 10 3f 70 21 61 94 00 04 |a...P....?p!a...| 00000020 00 00 00 01 61 a3 00 08 50 00 c5 00 10 3f 70 20 |....a...P....?p | 00000030 03 28 00 18 6e 61 61 2e 35 30 30 30 43 35 30 30 |.(..naa.5000C500| 00000040 31 30 33 46 37 30 32 30 00 00 00 00 00 00 00 00 |103F7020........| 00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000000f0 Or, if you want nicer output, try installing the sg3_utils package. It will fully decode page 0x83: # sg_inq -i da16 VPD INQUIRY: Device Identification page Designation descriptor number 1, descriptor length: 12 designator_type: NAA, code_set: Binary associated with the addressed logical unit NAA 5, IEEE Company_id: 0xc50 Vendor Specific Identifier: 0x103f7023 [0x5000c500103f7023] Designation descriptor number 2, descriptor length: 12 transport: Serial Attached SCSI (SAS) designator_type: NAA, code_set: Binary associated with the target port NAA 5, IEEE Company_id: 0xc50 Vendor Specific Identifier: 0x103f7021 [0x5000c500103f7021] Designation descriptor number 3, descriptor length: 8 transport: Serial Attached SCSI (SAS) designator_type: Relative target port, code_set: Binary associated with the target port Relative target port: 0x1 Designation descriptor number 4, descriptor length: 12 transport: Serial Attached SCSI (SAS) designator_type: NAA, code_set: Binary associated with the target device that contains addressed lu NAA 5, IEEE Company_id: 0xc50 Vendor Specific Identifier: 0x103f7020 [0x5000c500103f7020] Designation descriptor number 5, descriptor length: 28 designator_type: SCSI name string, code_set: UTF-8 associated with the target device that contains addressed lu SCSI name string: naa.5000C500103F7020 Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Wed Oct 9 16:33:23 2013 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 00251EEE; Wed, 9 Oct 2013 16:33:22 +0000 (UTC) (envelope-from dgilbert@interlog.com) Received: from smtp.infotech.no (smtp.infotech.no [82.134.31.41]) by mx1.freebsd.org (Postfix) with ESMTP id 9008623DF; Wed, 9 Oct 2013 16:33:22 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.infotech.no (Postfix) with ESMTP id 9DF6F204170; Wed, 9 Oct 2013 18:33:13 +0200 (CEST) X-Virus-Scanned: by amavisd-new-2.6.6 (20110518) (Debian) at infotech.no Received: from smtp.infotech.no ([127.0.0.1]) by localhost (smtp.infotech.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rxUpffBNxS5c; Wed, 9 Oct 2013 18:33:13 +0200 (CEST) Received: from [10.7.0.30] (unknown [10.7.0.30]) by smtp.infotech.no (Postfix) with ESMTPA id 867F720411D; Wed, 9 Oct 2013 18:33:12 +0200 (CEST) Message-ID: <52558521.7080408@interlog.com> Date: Wed, 09 Oct 2013 12:32:33 -0400 From: Douglas Gilbert User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: "Kenneth D. Merry" , Bj?rn Larsson Subject: Re: camcontrol cmd -c - for listing EVPD 0x83 References: <002701cec4e9$f5078d60$df16a820$@gmail.com> <20131009155731.GA43480@nargothrond.kdm.org> In-Reply-To: <20131009155731.GA43480@nargothrond.kdm.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-scsi@freebsd.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: dgilbert@interlog.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 16:33:23 -0000 On 13-10-09 11:57 AM, Kenneth D. Merry wrote: > On Wed, Oct 09, 2013 at 14:20:34 +0200, Bj?rn Larsson wrote: >> Dear All, >> >> >> >> I am trying to use ?camcontrol cmd ?c? to send a scsi inquiry command that >> lists 0x83 (device identification) data instead of the standard output given >> by the ?camcontrol inquiry? but I cannot get it to work properly. This could >> be due to that I am not understanding the hex format, so hopefully someone >> out there can point me in the right direction? The only information I am >> looking for is the WWN identifier of the SAS target. >> >> >> >> I have tried to create a SCSI CDB command according the information on: >> >> http://en.wikipedia.org/wiki/SCSI_Inquiry_Command and come up with the >> following command: >> >> >> >> # camcontrol cmd da0 ?c 0x009600830112 ?i 96 ? >> >> >> >> 12 is inquiry >> >> 01 EVPD bit is set >> >> 83 VPD Page >> >> 00 MSB length >> >> 96 LSB length >> >> 00 reserved > > The command isn't one hexadecimal number, but rather individual hexadecimal > numbers for each byte in the CDB. > > You also need to specify either "-" to direct the output to stdout, or > specify the output format. > > For example: > > # camcontrol cmd da16 -v -c "12 1 83 0 ff 0" -i 0xff - |hd > 00000000 00 83 00 48 01 03 00 08 50 00 c5 00 10 3f 70 23 |...H....P....?p#| > 00000010 61 93 00 08 50 00 c5 00 10 3f 70 21 61 94 00 04 |a...P....?p!a...| > 00000020 00 00 00 01 61 a3 00 08 50 00 c5 00 10 3f 70 20 |....a...P....?p | > 00000030 03 28 00 18 6e 61 61 2e 35 30 30 30 43 35 30 30 |.(..naa.5000C500| > 00000040 31 30 33 46 37 30 32 30 00 00 00 00 00 00 00 00 |103F7020........| > 00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| > * > 000000f0 > > Or, if you want nicer output, try installing the sg3_utils package. It > will fully decode page 0x83: > > # sg_inq -i da16 > VPD INQUIRY: Device Identification page > Designation descriptor number 1, descriptor length: 12 > designator_type: NAA, code_set: Binary > associated with the addressed logical unit > NAA 5, IEEE Company_id: 0xc50 > Vendor Specific Identifier: 0x103f7023 > [0x5000c500103f7023] > Designation descriptor number 2, descriptor length: 12 > transport: Serial Attached SCSI (SAS) > designator_type: NAA, code_set: Binary > associated with the target port > NAA 5, IEEE Company_id: 0xc50 > Vendor Specific Identifier: 0x103f7021 > [0x5000c500103f7021] > Designation descriptor number 3, descriptor length: 8 > transport: Serial Attached SCSI (SAS) > designator_type: Relative target port, code_set: Binary > associated with the target port > Relative target port: 0x1 > Designation descriptor number 4, descriptor length: 12 > transport: Serial Attached SCSI (SAS) > designator_type: NAA, code_set: Binary > associated with the target device that contains addressed lu > NAA 5, IEEE Company_id: 0xc50 > Vendor Specific Identifier: 0x103f7020 > [0x5000c500103f7020] > Designation descriptor number 5, descriptor length: 28 > designator_type: SCSI name string, code_set: UTF-8 > associated with the target device that contains addressed lu > SCSI name string: > naa.5000C500103F7020 More and more information is being placed in SCSI VPD pages (and in some cases removed from other non-obvious places). So sg3_utils has a utility specifically for looking at VPD pages: sg_vpd . sg_vpd also decodes some vendor specific VPD pages. So these days the VPD pages in sg_inq are in legacy mode while sg_vpd and sdparm (in a package called sdparm) have up to date VPD pages. That said, important and long standing VPD pages like the device identification VPD page (0x83) are kept up to date in sg_inq, sg_vpd and sdparm. sg_vpd (and sdparm) will also break down the device identification VPD page into component parts. 'sg_vpd -i ', 'sg_vpd -p di ' and 'sg_vpd -p 0x83 ' output all of the DI page. For smaller pieces: # sg_vpd -p di_lu da0 Device Identification VPD page: Addressed logical unit: designator type: NAA, code set: Binary 0x5000c50005b32003 # sg_vpd -p di_port da0 Device Identification VPD page: Target port: designator type: NAA, code set: Binary transport: Serial Attached SCSI Protocol (SPL-2) 0x5000c50005b32001 designator type: Relative target port, code set: Binary transport: Serial Attached SCSI Protocol (SPL-2) Relative target port: 0x1 # sdparm -p di_target da0 Device Identification VPD page: Target device that contains addressed lu: designator type: NAA, code set: Binary transport: Serial Attached SCSI Protocol (SPL-2) 0x5000c50005b32000 designator type: SCSI name string, code set: UTF-8 SCSI name string: naa.5000C50005B32000 And to suppress the verbosity: ]# sg_vpd -iq /dev/da0 0x5000c50005b32003 0x5000c50005b32001,0x1 0x5000c50005b32000 naa.5000C50005B32000 Doug Gilbert From owner-freebsd-scsi@FreeBSD.ORG Fri Oct 11 12:37:06 2013 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 146A4441; Fri, 11 Oct 2013 12:37:06 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-x22d.google.com (mail-oa0-x22d.google.com [IPv6:2607:f8b0:4003:c02::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 94581221E; Fri, 11 Oct 2013 12:37:05 +0000 (UTC) Received: by mail-oa0-f45.google.com with SMTP id o17so2367014oag.32 for ; Fri, 11 Oct 2013 05:37:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qRAJ5+Fweq5riYSRWT0qVTvhYUPEfYkCMziahkj9NlM=; b=YR40qGcOOht/xw6ImDaWTWq+6ytzcmhRIfdAca+CNUnsZSay8h4Y6evpADYOLtloYx 6hPF+PhFOj5RRVF5hwOozEEUKfaWhPRyA+wcIG+0Qs43LOI7wXgMh5X4jZ6Be6bfL5HZ EHclXyDvUuMLb2DaCmsyg+UOdHud4+RpntYppoPYmfsrbU9UpO/78Mt3GtTiLP+PsJoF +xZ6z1k9e4ShYmr5axM/8Sw7BBVrAKCMQiP3niJU6/BW/awixNNmUPbinn6ZCaRkOkRN gjW/mzxgEwQeNY/8mCjoxcu8P3MQepiCt7GTmdXgSgECFU0MV7baLUg1TrREO6UK5dhv RB7w== MIME-Version: 1.0 X-Received: by 10.60.63.9 with SMTP id c9mr14133184oes.35.1381495024552; Fri, 11 Oct 2013 05:37:04 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Fri, 11 Oct 2013 05:37:04 -0700 (PDT) In-Reply-To: References: <522A1C73.9030402@mu.org> Date: Fri, 11 Oct 2013 08:37:04 -0400 Message-ID: Subject: Re: New iSCSI stack. From: Outback Dingo To: =?ISO-8859-2?Q?Edward_Tomasz_Napiera=B3a?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-scsi@freebsd.org, "freebsd-arch@freebsd.org" , Alfred Perlstein , "freebsd-current@FreeBSD.org" X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 12:37:06 -0000 On Wed, Sep 11, 2013 at 5:14 PM, Edward Tomasz Napiera=C5=82a wrote: > I'm working on last few minor nits to get this into the tree. Give me fe= w > days, > I'll prepare a patch against 9-STABLE. > > Quick question, is there a specific reason why ctld doesnt create the file / device for iscsi, or fc ? the previous iscsi would read the config file and create the file / device ... it now appears to be a manual process.