From owner-freebsd-scsi@FreeBSD.ORG Mon May 23 11:07:07 2011 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83BA11065674 for ; Mon, 23 May 2011 11:07:07 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 739438FC20 for ; Mon, 23 May 2011 11:07:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4NB77Q8051790 for ; Mon, 23 May 2011 11:07:07 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4NB76IL051788 for freebsd-scsi@FreeBSD.org; Mon, 23 May 2011 11:07:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 May 2011 11:07:06 GMT Message-Id: <201105231107.p4NB76IL051788@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 Cc: Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2011 11:07:07 -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/154432 scsi [xpt] run_interrupt_driven_hooks: still waiting after o kern/153361 scsi [ciss] Smart Array 5300 boot/detect drive problem o kern/152250 scsi [ciss] [patch] Kernel panic when hw.ciss.expose_hidden o kern/151564 scsi [ciss] ciss(4) should increase CISS_MAX_LOGICAL to 10 o docs/151336 scsi Missing documentation of scsi_ and ata_ functions in c s kern/149927 scsi [cam] hard drive not stopped before removing power dur o kern/148083 scsi [aac] Strange device reporting o kern/147704 scsi [mpt] sys/dev/mpt: new chip revision, partially unsupp o kern/146287 scsi [ciss] ciss(4) cannot see more than one SmartArray con o kern/145768 scsi [mpt] can't perform I/O on SAS based SAN disk in freeb o kern/144648 scsi [aac] Strange values of speed and bus width in dmesg o kern/144301 scsi [ciss] [hang] HP proliant server locks when using ciss o kern/142351 scsi [mpt] LSILogic driver performance problems o kern/141934 scsi [cam] [patch] add support for SEAGATE DAT Scopion 130 o kern/134488 scsi [mpt] MPT SCSI driver probes max. 8 LUNs per device o kern/132250 scsi [ciss] ciss driver does not support more then 15 drive o kern/132206 scsi [mpt] system panics on boot when mirroring and 2nd dri o kern/130621 scsi [mpt] tranfer rate is inscrutable slow when use lsi213 o kern/129602 scsi [ahd] ahd(4) gets confused and wedges SCSI bus o kern/128452 scsi [sa] [panic] Accessing SCSI tape drive randomly crashe o kern/128245 scsi [scsi] "inquiry data fails comparison at DV1 step" [re o kern/127927 scsi [isp] isp(4) target driver crashes kernel when set up o kern/127717 scsi [ata] [patch] [request] - support write cache toggling o kern/124667 scsi [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi o kern/123674 scsi [ahc] ahc driver dumping o kern/123520 scsi [ahd] unable to boot from net while using ahd o sparc/121676 scsi [iscsi] iscontrol do not connect iscsi-target on sparc o kern/120487 scsi [sg] scsi_sg incompatible with scanners o kern/120247 scsi [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s o kern/114597 scsi [sym] System hangs at SCSI bus reset with dual HBAs o kern/110847 scsi [ahd] Tyan U320 onboard problem with more than 3 disks o kern/99954 scsi [ahc] reading from DVD failes on 6.x [regression] o kern/92798 scsi [ahc] SCSI problem with timeouts o kern/90282 scsi [sym] SCSI bus resets cause loss of ch device o kern/76178 scsi [ahd] Problem with ahd and large SCSI Raid system o kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5.3 s kern/61165 scsi [panic] kernel page fault after calling cam_send_ccb o kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C810 under load o kern/60598 scsi wire down of scsi devices conflicts with config s kern/57398 scsi [mly] Current fails to install on mly(4) based RAID di o bin/57088 scsi [cam] [patch] for a possible fd leak in libcam.c o kern/52638 scsi [panic] SCSI U320 on SMP server won't run faster than o kern/44587 scsi dev/dpt/dpt.h is missing defines required for DPT_HAND o kern/39388 scsi ncr/sym drivers fail with 53c810 and more than 256MB m o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce 45 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon May 23 21:09:55 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F3FE106566B for ; Mon, 23 May 2011 21:09:55 +0000 (UTC) (envelope-from toomas.aas@raad.tartu.ee) Received: from kuller.raad.tartu.ee (kuller.raad.tartu.ee [213.184.43.8]) by mx1.freebsd.org (Postfix) with ESMTP id 4F2498FC13 for ; Mon, 23 May 2011 21:09:55 +0000 (UTC) Received: from kuller.raad.tartu.ee (localhost [127.0.0.1]) by kuller.raad.tartu.ee (Postfix) with ESMTP id 72A1139828 for ; Tue, 24 May 2011 00:09:53 +0300 (EEST) X-Virus-Scanned: amavisd-new at post.raad.tartu.ee Received: from kuller.raad.tartu.ee ([127.0.0.1]) by kuller.raad.tartu.ee (kuller.raad.tartu.ee [127.0.0.1]) (amavisd-new, port 10024) with LMTP id j66aXNcCKjJ9 for ; Tue, 24 May 2011 00:09:21 +0300 (EEST) Received: by kuller.raad.tartu.ee (Postfix, from userid 80) id 477583985C; Tue, 24 May 2011 00:09:21 +0300 (EEST) Received: from 226.16.50.84.dyn.estpak.ee (226.16.50.84.dyn.estpak.ee [84.50.16.226]) by webmail.raad.tartu.ee (Horde Framework) with HTTP; Tue, 24 May 2011 00:09:21 +0300 Message-ID: <20110524000921.10862o7lpz7ezx8g@webmail.raad.tartu.ee> Date: Tue, 24 May 2011 00:09:21 +0300 From: Toomas Aas To: freebsd-scsi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.7) X-Originating-IP: 84.50.16.226 Subject: iSCSI multipathing X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2011 21:09:55 -0000 Now that I have basic iSCSI connection working with FreeBSD 7.3 (thanks Danny!) I'm looking at multipathing. My server has two dedicated interfaces for iSCSI traffic, each connected to a separate gigabit switch, and each switch in turn connected to a separate interface on my iSCSI target (EMC Celerra NX4). I can bring up either of the two connections with iscontrol, mount the partition from the target and use it to my heart's content. But how should I handle multipathing? My initial thought was to bring up both connections simultaneously and set up gmultipath across da0 and da1. However, as soon as I bring up both connections, it seems that they begin to constantly disconnecting and reconnecting: # iscontrol -c /etc/iscsi.conf -n celerra_path1 iscontrol[14277]: running iscontrol[14277]: (pass0:iscsi0:0:0:2): tagged openings now 0 # iscontrol -c /etc/iscsi.conf -n celerra_path2 iscontrol[14277]: trapped signal 30 trapped signal 30 iscontrol: supervise going down iscontrol[14277]: sess flags=2000040d iscontrol[14277]: Reconnect iscontrol[14309]: running iscontrol[14309]: (pass1:iscsi1:0:0:2): tagged openings now 0 iscontrol[14309]: trapped signal 30 trapped signal 30 iscontrol: supervise going down iscontrol[14309]: sess flags=2000040d iscontrol[14309]: Reconnect iscontrol[14277]: trapped signal 30 trapped signal 30 iscontrol: supervise going down iscontrol[14277]: sess flags=2000040d iscontrol[14277]: Reconnect iscontrol[14309]: trapped signal 30 trapped signal 30 iscontrol: supervise going down iscontrol[14309]: sess flags=2000040d iscontrol[14309]: Reconnect iscontrol[14277]: trapped signal 30 trapped signal 30 iscontrol: supervise going down iscontrol[14277]: sess flags=2000040d iscontrol[14277]: Reconnect Is there a way to avoid this constant disconnect/reconnect? How are other people handling multipathing on iSCSI? -- Toomas Aas From owner-freebsd-scsi@FreeBSD.ORG Mon May 23 21:28:54 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7DA11065675 for ; Mon, 23 May 2011 21:28:54 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 702C68FC12 for ; Mon, 23 May 2011 21:28:54 +0000 (UTC) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.14.4/8.14.4) with ESMTP id p4NLSrj1072437 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 May 2011 14:28:53 -0700 (PDT) (envelope-from mj@feral.com) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.14.4/8.14.4/Submit) with ESMTP id p4NLSqED072427; Mon, 23 May 2011 14:28:52 -0700 (PDT) (envelope-from mj@feral.com) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Mon, 23 May 2011 14:28:52 -0700 (PDT) From: Matthew Jacob To: Toomas Aas In-Reply-To: <20110524000921.10862o7lpz7ezx8g@webmail.raad.tartu.ee> Message-ID: References: <20110524000921.10862o7lpz7ezx8g@webmail.raad.tartu.ee> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (ns1.feral.com [127.0.0.1]); Mon, 23 May 2011 14:28:53 -0700 (PDT) Cc: freebsd-scsi@freebsd.org Subject: Re: iSCSI multipathing X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mj@feral.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2011 21:28:54 -0000 Oh, I suspect that this won't work because you're likely confusing the target as to which connection you're coming from. That is, multipathing and iSCSI needs network multipathing, not geom multipathing. On Tue, 24 May 2011, Toomas Aas wrote: > Now that I have basic iSCSI connection working with FreeBSD 7.3 (thanks > Danny!) I'm looking at multipathing. My server has two dedicated interfaces > for iSCSI traffic, each connected to a separate gigabit switch, and each > switch in turn connected to a separate interface on my iSCSI target (EMC > Celerra NX4). I can bring up either of the two connections with iscontrol, > mount the partition from the target and use it to my heart's content. But how > should I handle multipathing? > > My initial thought was to bring up both connections simultaneously and set up > gmultipath across da0 and da1. However, as soon as I bring up both > connections, it seems that they begin to constantly disconnecting and > reconnecting: > > # iscontrol -c /etc/iscsi.conf -n celerra_path1 > iscontrol[14277]: running > iscontrol[14277]: (pass0:iscsi0:0:0:2): tagged openings now 0 > > # iscontrol -c /etc/iscsi.conf -n celerra_path2 > iscontrol[14277]: trapped signal 30 > trapped signal 30 > iscontrol: supervise going down > iscontrol[14277]: sess flags=2000040d > iscontrol[14277]: Reconnect > iscontrol[14309]: running > iscontrol[14309]: (pass1:iscsi1:0:0:2): tagged openings now 0 > iscontrol[14309]: trapped signal 30 > trapped signal 30 > iscontrol: supervise going down > iscontrol[14309]: sess flags=2000040d > iscontrol[14309]: Reconnect > iscontrol[14277]: trapped signal 30 > trapped signal 30 > iscontrol: supervise going down > iscontrol[14277]: sess flags=2000040d > iscontrol[14277]: Reconnect > iscontrol[14309]: trapped signal 30 > trapped signal 30 > iscontrol: supervise going down > iscontrol[14309]: sess flags=2000040d > iscontrol[14309]: Reconnect > iscontrol[14277]: trapped signal 30 > trapped signal 30 > iscontrol: supervise going down > iscontrol[14277]: sess flags=2000040d > iscontrol[14277]: Reconnect > > Is there a way to avoid this constant disconnect/reconnect? How are other > people handling multipathing on iSCSI? > > -- > Toomas Aas > > _______________________________________________ > 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" From owner-freebsd-scsi@FreeBSD.ORG Tue May 24 04:53:41 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 887BE106564A for ; Tue, 24 May 2011 04:53:41 +0000 (UTC) (envelope-from toomas.aas@raad.tartu.ee) Received: from kuller.raad.tartu.ee (kuller.raad.tartu.ee [213.184.43.8]) by mx1.freebsd.org (Postfix) with ESMTP id 35B988FC0C for ; Tue, 24 May 2011 04:53:41 +0000 (UTC) Received: from kuller.raad.tartu.ee (localhost [127.0.0.1]) by kuller.raad.tartu.ee (Postfix) with ESMTP id 2413339846; Tue, 24 May 2011 07:53:40 +0300 (EEST) X-Virus-Scanned: amavisd-new at post.raad.tartu.ee Received: from kuller.raad.tartu.ee ([127.0.0.1]) by kuller.raad.tartu.ee (kuller.raad.tartu.ee [127.0.0.1]) (amavisd-new, port 10024) with LMTP id beq6+a6r1dfz; Tue, 24 May 2011 07:53:38 +0300 (EEST) Received: by kuller.raad.tartu.ee (Postfix, from userid 80) id 690A739847; Tue, 24 May 2011 07:53:38 +0300 (EEST) Received: from 226.16.50.84.dyn.estpak.ee (226.16.50.84.dyn.estpak.ee [84.50.16.226]) by webmail.raad.tartu.ee (Horde Framework) with HTTP; Tue, 24 May 2011 07:53:38 +0300 Message-ID: <20110524075338.97072kalk6qhm1gk@webmail.raad.tartu.ee> Date: Tue, 24 May 2011 07:53:38 +0300 From: Toomas Aas To: mj@feral.com References: <20110524000921.10862o7lpz7ezx8g@webmail.raad.tartu.ee> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.7) X-Originating-IP: 84.50.16.226 Cc: freebsd-scsi@freebsd.org Subject: Re: iSCSI multipathing X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2011 04:53:41 -0000 T, 24 mai 2011 kirjutas Matthew Jacob : > > Oh, I suspect that this won't work because you're likely confusing > the target as to which connection you're coming from. > > That is, multipathing and iSCSI needs network multipathing, not geom > multipathing. OK, Thanks for the explanation. I hate to be the "it works on Linux" guy, but it really does ;) I have several Linux boxes connecting to the same EMC Celerra using Device Mapper multipathing. I was hoping that gmultipath does the same job on FreeBSD, but apparently then it doesn't. -- Toomas Aas From owner-freebsd-scsi@FreeBSD.ORG Tue May 24 11:25:17 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C802F106566C for ; Tue, 24 May 2011 11:25:17 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 90BD78FC12 for ; Tue, 24 May 2011 11:25:17 +0000 (UTC) Received: from [192.168.135.100] (c-76-126-155-117.hsd1.ca.comcast.net [76.126.155.117]) (authenticated bits=0) by ns1.feral.com (8.14.4/8.14.4) with ESMTP id p4OBP9Oj089656 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 24 May 2011 04:25:11 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <4DDB9596.5010301@feral.com> Date: Tue, 24 May 2011 04:25:10 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <20110524000921.10862o7lpz7ezx8g@webmail.raad.tartu.ee> <20110524075338.97072kalk6qhm1gk@webmail.raad.tartu.ee> In-Reply-To: <20110524075338.97072kalk6qhm1gk@webmail.raad.tartu.ee> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (ns1.feral.com [192.67.166.1]); Tue, 24 May 2011 04:25:16 -0700 (PDT) Subject: Re: iSCSI multipathing X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2011 11:25:17 -0000 Hmm? Really? Oh, well. In linux is it using one of the RDAC drivers? I assume you're using openiscsi. Perhaps openiscsi is helping here. In any case, I doubt we're going to fix it today. On 5/23/2011 9:53 PM, Toomas Aas wrote: > T, 24 mai 2011 kirjutas Matthew Jacob : > >> >> Oh, I suspect that this won't work because you're likely confusing >> the target as to which connection you're coming from. >> >> That is, multipathing and iSCSI needs network multipathing, not geom >> multipathing. > > OK, Thanks for the explanation. > > I hate to be the "it works on Linux" guy, but it really does ;) I have > several Linux boxes connecting to the same EMC Celerra using Device > Mapper multipathing. I was hoping that gmultipath does the same job on > FreeBSD, but apparently then it doesn't. > From owner-freebsd-scsi@FreeBSD.ORG Tue May 24 12:22:36 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6FFE81065670 for ; Tue, 24 May 2011 12:22:36 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id EF58D8FC1C for ; Tue, 24 May 2011 12:22:34 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1QOqI2-0000Hy-NI for freebsd-scsi@freebsd.org; Tue, 24 May 2011 15:00:46 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: freebsd-scsi@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 May 2011 15:00:46 +0300 From: Daniel Braniss Message-ID: Subject: iscsi_initiator and tag opening problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2011 12:22:36 -0000 Hi all, I'm having problems with particular iscsi-targets, which when increasing the tag opening above 1, will crash the target. The developers are saying that they do suport tagged queuing, but 'do not support task-set management (which is what initiator side attempts at controlling target side execution ordering is called)' So, since I'm the iscsi_initiator developer, is there any way that I can tell the CAM to keep it SIMPLE as opposed to ORDERED? Sorry, my knowledge of ISCSI stopped at version 2 :-) thanks, danny From owner-freebsd-scsi@FreeBSD.ORG Tue May 24 13:34:53 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56FA51065673 for ; Tue, 24 May 2011 13:34:53 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 212578FC16 for ; Tue, 24 May 2011 13:34:52 +0000 (UTC) Received: from [192.168.135.100] (c-76-126-155-117.hsd1.ca.comcast.net [76.126.155.117]) (authenticated bits=0) by ns1.feral.com (8.14.4/8.14.4) with ESMTP id p4ODYoZg037200 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 24 May 2011 06:34:52 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <4DDBB3F7.20303@feral.com> Date: Tue, 24 May 2011 06:34:47 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (ns1.feral.com [192.67.166.1]); Tue, 24 May 2011 06:34:52 -0700 (PDT) Subject: Re: iscsi_initiator and tag opening problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2011 13:34:53 -0000 First of all, the target is broken here, but okay. Secondly, you, as the entity forming up PDUs and BHS entities can put whatever tag you want in it, no? The DA driver uses an ordered tag every now and then (foolishly- there's a sysctl to turn that off). On 5/24/2011 5:00 AM, Daniel Braniss wrote: > Hi all, > I'm having problems with particular iscsi-targets, which when increasing > the tag opening above 1, will crash the target. The developers are > saying that they do suport tagged queuing, but > > 'do not support task-set management (which is what initiator side > attempts at controlling target side execution ordering is called)' > > So, since I'm the iscsi_initiator developer, is there any way that I can tell > the CAM to keep it SIMPLE as opposed to ORDERED? > Sorry, my knowledge of ISCSI stopped at version 2 :-) > > thanks, > danny > > > _______________________________________________ > 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" From owner-freebsd-scsi@FreeBSD.ORG Tue May 24 14:14:04 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3DB1106564A for ; Tue, 24 May 2011 14:14:04 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 9298F8FC13 for ; Tue, 24 May 2011 14:14:04 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1QOsMz-00028p-LN; Tue, 24 May 2011 17:14:01 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Matthew Jacob In-reply-to: <4DDBB3F7.20303@feral.com> References: <4DDBB3F7.20303@feral.com> Comments: In-reply-to Matthew Jacob message dated "Tue, 24 May 2011 06:34:47 -0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 May 2011 17:14:01 +0300 From: Daniel Braniss Message-ID: Cc: freebsd-scsi@freebsd.org Subject: Re: iscsi_initiator and tag opening problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2011 14:14:04 -0000 > First of all, the target is broken here, but okay. yeh, but 'it works with MS' :-( the first one with the problem was iscilon, but today, something similar i'm seeing with IBM storewiz. > > Secondly, you, as the entity forming up PDUs and BHS entities can put > whatever tag you want in it, no? > The DA driver uses an ordered tag every now and then (foolishly- there's > a sysctl to turn that off). > it's a CAM thing not PDU/BHS, or at least that is my undertanding. myabe it's time to read the RFC again > On 5/24/2011 5:00 AM, Daniel Braniss wrote: > > Hi all, > > I'm having problems with particular iscsi-targets, which when increasing > > the tag opening above 1, will crash the target. The developers are > > saying that they do suport tagged queuing, but > > > > 'do not support task-set management (which is what initiator side > > attempts at controlling target side execution ordering is called)' > > > > So, since I'm the iscsi_initiator developer, is there any way that I can tell > > the CAM to keep it SIMPLE as opposed to ORDERED? > > Sorry, my knowledge of ISCSI stopped at version 2 :-) > > > > thanks, > > danny > > > > > > _______________________________________________ > > 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" > _______________________________________________ > 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" > From owner-freebsd-scsi@FreeBSD.ORG Tue May 24 18:20:27 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 981B11065670 for ; Tue, 24 May 2011 18:20:27 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 413838FC16 for ; Tue, 24 May 2011 18:20:26 +0000 (UTC) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.14.4/8.14.4) with ESMTP id p4OIJnUr040365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 24 May 2011 11:19:49 -0700 (PDT) (envelope-from mj@feral.com) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.14.4/8.14.4/Submit) with ESMTP id p4OIJmuQ040362; Tue, 24 May 2011 11:19:49 -0700 (PDT) (envelope-from mj@feral.com) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Tue, 24 May 2011 11:19:48 -0700 (PDT) From: Matthew Jacob To: Daniel Braniss In-Reply-To: Message-ID: References: <4DDBB3F7.20303@feral.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (ns1.feral.com [127.0.0.1]); Tue, 24 May 2011 11:19:49 -0700 (PDT) Cc: freebsd-scsi@freebsd.org Subject: Re: iscsi_initiator and tag opening problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mj@feral.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2011 18:20:27 -0000 > > it's a CAM thing not PDU/BHS, or at least that is my undertanding. > myabe it's time to read the RFC again > No, what I meant can be seen in the following from iscsi_subr.c: /* | map tag option, default is UNTAGGED */ switch(csio->tag_action) { case MSG_SIMPLE_Q_TAG: cmd->attr = iSCSI_TASK_SIMPLE; break; case MSG_HEAD_OF_Q_TAG: cmd->attr = iSCSI_TASK_HOFQ; break; case MSG_ORDERED_Q_TAG: cmd->attr = iSCSI_TASK_ORDER; break; case MSG_ACA_TASK: cmd->attr = iSCSI_TASK_ACA; break; } That is, you're translating from CAM to iSCSI task attributes. Or, rather, iSCSI transport related task attributes. The same thing can be seen in the isp FibreChannel driver: if (ttype == REQFLAG_OTAG) { ttype = FCP_CMND_TASK_ATTR_ORDERED; } else if (ttype == REQFLAG_HTAG) { ttype = FCP_CMND_TASK_ATTR_HEAD; } else { ttype = FCP_CMND_TASK_ATTR_SIMPLE; } ((ispreqt7_t *)reqp)->req_task_attribute = ttype; (yes, mine is skipping ACA, oops) These are attributes of SAM task management. CAM, like any other SCSI midlayer, is quite right to attach the specified attribute. Whether the underlying transport can faithfully support those attributes is another matter. The RFC has the following: 3.5.1.1. SCSI-Command This request carries the SCSI CDB and all the other SCSI execute command procedure call (see [SAM2]) IN arguments such as task attributes, Expected Data Transfer Length for one or both transfer directions This would imply that iSCSI is supposed to support task attributes. Now, it turns out that the linux openiscsi implementation only uses the iSCSI_TASK_SIMPLE attribute, so perhaps the simplest fix here is to just do that for the FreeBSD initiator driver. From owner-freebsd-scsi@FreeBSD.ORG Wed May 25 07:20:46 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45EA3106566C for ; Wed, 25 May 2011 07:20:46 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 02BAA8FC1B for ; Wed, 25 May 2011 07:20:45 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1QP8OZ-000CmK-GP; Wed, 25 May 2011 10:20:43 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: mj@feral.com In-reply-to: References: <4DDBB3F7.20303@feral.com> Comments: In-reply-to Matthew Jacob message dated "Tue, 24 May 2011 11:19:48 -0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 May 2011 10:20:43 +0300 From: Daniel Braniss Message-ID: Cc: freebsd-scsi@freebsd.org Subject: Re: iscsi_initiator and tag opening problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 May 2011 07:20:46 -0000 > > > > it's a CAM thing not PDU/BHS, or at least that is my undertanding. > > myabe it's time to read the RFC again > > > > No, what I meant can be seen in the following from iscsi_subr.c: > > /* > | map tag option, default is UNTAGGED > */ > switch(csio->tag_action) { > case MSG_SIMPLE_Q_TAG: cmd->attr = iSCSI_TASK_SIMPLE; break; > case MSG_HEAD_OF_Q_TAG: cmd->attr = iSCSI_TASK_HOFQ; break; > case MSG_ORDERED_Q_TAG: cmd->attr = iSCSI_TASK_ORDER; break; > case MSG_ACA_TASK: cmd->attr = iSCSI_TASK_ACA; break; > } > how emabarrassing! in my defense I wrote this back in 2004 and never looked at it again :-) > > That is, you're translating from CAM to iSCSI task attributes. Or, rather, > iSCSI transport related task attributes. The same thing can be seen in the > isp FibreChannel driver: > > if (ttype == REQFLAG_OTAG) { > ttype = FCP_CMND_TASK_ATTR_ORDERED; > } else if (ttype == REQFLAG_HTAG) { > ttype = FCP_CMND_TASK_ATTR_HEAD; > } else { > ttype = FCP_CMND_TASK_ATTR_SIMPLE; > } > ((ispreqt7_t *)reqp)->req_task_attribute = ttype; > > (yes, mine is skipping ACA, oops) > > These are attributes of SAM task management. CAM, like any other SCSI > midlayer, is quite right to attach the specified attribute. Whether the > underlying transport can faithfully support those attributes is another > matter. is this somehow detectable? or a list of '[non]complaint' targets is needed? > > The RFC has the following: > > 3.5.1.1. SCSI-Command > > This request carries the SCSI CDB and all the other SCSI execute > command procedure call (see [SAM2]) IN arguments such as task > attributes, Expected Data Transfer Length for one or both transfer > directions > > This would imply that iSCSI is supposed to support task attributes. > > Now, it turns out that the linux openiscsi implementation only uses the > iSCSI_TASK_SIMPLE attribute, so perhaps the simplest fix here is to just > do that for the FreeBSD initiator driver. any side effects? or should I make it tunable? Thanks Matthew, you made my day! danny From owner-freebsd-scsi@FreeBSD.ORG Wed May 25 13:49:47 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07BB61065670 for ; Wed, 25 May 2011 13:49:47 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id C3A348FC15 for ; Wed, 25 May 2011 13:49:46 +0000 (UTC) Received: from [192.168.135.103] (c-76-126-155-117.hsd1.ca.comcast.net [76.126.155.117]) (authenticated bits=0) by ns1.feral.com (8.14.4/8.14.4) with ESMTP id p4PDnAjr096278 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 25 May 2011 06:49:12 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <4DDD08D6.30105@feral.com> Date: Wed, 25 May 2011 06:49:10 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Daniel Braniss References: <4DDBB3F7.20303@feral.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (ns1.feral.com [192.67.166.1]); Wed, 25 May 2011 06:49:12 -0700 (PDT) Cc: freebsd-scsi@freebsd.org Subject: Re: iscsi_initiator and tag opening problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 May 2011 13:49:47 -0000 On 5/25/2011 12:20 AM, Daniel Braniss wrote: > ... > is this somehow detectable? or a list of '[non]complaint' targets is needed? You probably should decide whether to just use SIMPLE (no matter what) or have a list. Since it's a violation of SAM I doubt that there is a way to detect it. > ... > any side effects? or should I make it tunable? As it stands now for FreeBSD, making them all SIMPLE would probably be okay. Linux does that apparently. I'd make it a tunable with the default to SIMPLE. I asked some of the (now NetApp) Engenio engineers, and their arrays' iSCSI implementation *does* handle all of the different tag types. > Thanks Matthew, you made my day! > > No problem. Thank you, actually. I'm starting to work more with iSCSI for my day job which has been an interesting change. From owner-freebsd-scsi@FreeBSD.ORG Wed May 25 14:36:25 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EEF031065670 for ; Wed, 25 May 2011 14:36:25 +0000 (UTC) (envelope-from toomas.aas@raad.tartu.ee) Received: from kuller.raad.tartu.ee (kuller.raad.tartu.ee [213.184.43.8]) by mx1.freebsd.org (Postfix) with ESMTP id 993CC8FC12 for ; Wed, 25 May 2011 14:36:25 +0000 (UTC) Received: from kuller.raad.tartu.ee (localhost [127.0.0.1]) by kuller.raad.tartu.ee (Postfix) with ESMTP id 274B839842; Wed, 25 May 2011 17:36:24 +0300 (EEST) X-Virus-Scanned: amavisd-new at post.raad.tartu.ee Received: from kuller.raad.tartu.ee ([127.0.0.1]) by kuller.raad.tartu.ee (kuller.raad.tartu.ee [127.0.0.1]) (amavisd-new, port 10024) with LMTP id daERRLuQpGQF; Wed, 25 May 2011 17:36:22 +0300 (EEST) Received: by kuller.raad.tartu.ee (Postfix, from userid 80) id F080039832; Wed, 25 May 2011 17:36:21 +0300 (EEST) Received: from lv.raad.tartu.ee (lv.raad.tartu.ee [213.184.43.2]) by webmail.raad.tartu.ee (Horde Framework) with HTTP; Wed, 25 May 2011 17:36:21 +0300 Message-ID: <20110525173621.19686ehnri4qc60w@webmail.raad.tartu.ee> Date: Wed, 25 May 2011 17:36:21 +0300 From: Toomas Aas To: Matthew Jacob References: <20110524000921.10862o7lpz7ezx8g@webmail.raad.tartu.ee> <20110524075338.97072kalk6qhm1gk@webmail.raad.tartu.ee> <4DDB9596.5010301@feral.com> In-Reply-To: <4DDB9596.5010301@feral.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.7) X-Originating-IP: 213.184.43.2 Cc: freebsd-scsi@freebsd.org Subject: Re: iSCSI multipathing X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 May 2011 14:36:26 -0000 Hello, Matthew and others! > Hmm? Really? Oh, well. In linux is it using one of the RDAC drivers? > I assume you're using openiscsi. Perhaps openiscsi is helping here. It's not using RDAC drivers, it's openiscsi and DM-MPIO on top of that. I don't know which of these two components helps in this case, and anyway this knowledge wouldn't help me get things going on FreeBSD, so this is more of a theoretical point. Once again, thanks for taking time to explain things. -- Toomas Aas From owner-freebsd-scsi@FreeBSD.ORG Thu May 26 06:15:36 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 316DD106566B for ; Thu, 26 May 2011 06:15:36 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id D3D0B8FC12 for ; Thu, 26 May 2011 06:15:35 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1QPTr3-0001wu-9E; Thu, 26 May 2011 09:15:33 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Matthew Jacob In-reply-to: <4DDD08D6.30105@feral.com> References: <4DDBB3F7.20303@feral.com> <4DDD08D6.30105@feral.com> Comments: In-reply-to Matthew Jacob message dated "Wed, 25 May 2011 06:49:10 -0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 26 May 2011 09:15:33 +0300 From: Daniel Braniss Message-ID: Cc: freebsd-scsi@freebsd.org Subject: Re: iscsi_initiator and tag opening problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2011 06:15:36 -0000 > > > On 5/25/2011 12:20 AM, Daniel Braniss wrote: > > ... > > is this somehow detectable? or a list of '[non]complaint' targets is needed? > You probably should decide whether to just use SIMPLE (no matter what) > or have a list. Since it's a violation of SAM I doubt that there is a > way to detect it. > > ... > > any side effects? or should I make it tunable? > > As it stands now for FreeBSD, making them all SIMPLE would probably be > okay. Linux does that apparently. > I'd make it a tunable with the default to SIMPLE. I asked some of the > (now NetApp) Engenio engineers, and their arrays' iSCSI implementation > *does* handle all of the different tag types. I'm inclined to set the default as it was, and only if it doesn't work it can be fixed via the tunable. The reasoning is that it has worked for most targets, including NetAPP, but then again, if the new crop of targets are based on non-compliant ... > > Thanks Matthew, you made my day! > > > > > No problem. Thank you, actually. I'm starting to work more with iSCSI > for my day job which has been an interesting change. I hope it won't interfere with your valuable cooperation! cheers, danny From owner-freebsd-scsi@FreeBSD.ORG Fri May 27 07:01:22 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 969F61065673; Fri, 27 May 2011 07:01:22 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id BD1578FC08; Fri, 27 May 2011 07:01:21 +0000 (UTC) Received: by fxm11 with SMTP id 11so1633701fxm.13 for ; Fri, 27 May 2011 00:01:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:subject:x-enigmail-version:content-type :content-transfer-encoding; bh=l8VOcEWuo13BcahdsXx4E/NgKgbPpqSoU3BDcRgqJ/g=; b=wgbfj+fDuQA5XNp827481AMfl28cId6eIA0+Yz21a3IPq32vq9kIV30WsTymC6m2p8 /PmkMdlgutgBPYWfo6oUN2qkqslBz9FDDyrdQzUGOlrj8f+Q9STATfTC25v8fUgA1Mpk 6dCx2XBxXJaJoUyItE7hCIIR0LUBBde0KbuUk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :x-enigmail-version:content-type:content-transfer-encoding; b=NHCJcCOeZa4fIA1ZFQdrfGAydbuTNIILyEKku0dlKEZm+W1627vHGgNsohy04RP3dR x0yN0XwJy3ODq8agmg5v71qTc+Qom8IzEHq+xy+lTATA5grupkTpaRhbQvufJ52QeiAV 5tFFnsRMEkuM8L0o5URremgrNhwWH2u+TJNb0= Received: by 10.223.28.220 with SMTP id n28mr493044fac.101.1306479680500; Fri, 27 May 2011 00:01:20 -0700 (PDT) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id l26sm555292fah.38.2011.05.27.00.01.18 (version=SSLv3 cipher=OTHER); Fri, 27 May 2011 00:01:19 -0700 (PDT) Sender: Alexander Motin Message-ID: <4DDF4C23.3010600@FreeBSD.org> Date: Fri, 27 May 2011 10:00:51 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: freebsd-scsi@freebsd.org, FreeBSD-Current , freebsd-hardware@freebsd.org X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: Subject: SES/SAF-TE + SATA == SEMB! X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2011 07:01:22 -0000 Hi. As probably not many know, SATA specification defines the way to talk to SES/SAF-TE enclosures -- Serial ATA Enclosure Management Bridge (SEMB). It can be either separate device or built-in to SATA Port Multiplier. I know at leat two models of Port Multipliers including SEMB and having I2C interfaces to talk to SEP (backplane): SiI3726 and SiI4726. Unluckily such combination of hardware is not widely spread (backplanes are rarely used in desktops, while PMPs are rarely used in servers), but finally I've built such setup! I've connected SuperMicro SAS815TQ backplane to the SiI3726 multiplier with I2C cable and it works like a charm! I've made a patch for HEAD to support it. It adds SEMB devices support to the ATA/SATA XPT probe code, some glue to handle one more ATA-based command protocol and some changes to ses(4) driver to teach it talk to such devices: http://people.freebsd.org/~mav/semb.patch As result I've got: %dmesg |grep ses0 ses0 at ahcich8 bus 0 scbus8 target 5 lun 0 ses0: SEMB S-E-S 2.00 device ses0: Serial Number 50030481 ses0: 150.000MB/s transfers (SATA 1.x, NONE, PIO 8192bytes) ses0: SEMB SES Device ses0: GenCode 0 0 Subenclosures ses0: SubEnclosure ID 0, 4 Types With this ID, Enclosure Length 36 ses0: WWN: 3530303330343831 ses0: Type Desc[0]: Type 0x17, MaxElt 4, In Subenc 0, Text Length 0 ses0: Type Desc[1]: Type 0x4, MaxElt 1, In Subenc 0, Text Length 0 ses0: Type Desc[2]: Type 0xe, MaxElt 1, In Subenc 0, Text Length 0 ses0: Type Desc[3]: Type 0x6, MaxElt 1, In Subenc 0, Text Length 0 %camcontrol devlist at scbus8 target 0 lun 0 (ada0,pass1) at scbus8 target 1 lun 0 (ada1,pass2) at scbus8 target 2 lun 0 (pass5,ada2) at scbus8 target 3 lun 0 (pass6,ada3) at scbus8 target 5 lun 0 (ses0,pass3) at scbus8 target 15 lun 0 (pass4,pmp0) %getencstat -v /dev/ses0 /dev/ses0: Enclosure Status Element 0x0: Array device OK (Status=ok (bytes=0x11 0x00 0x00 0x00)) Element 0x1: Array device OK (Status=ok (bytes=0x11 0x00 0x00 0x00)) Element 0x2: Array device OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) Element 0x3: Array device OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) Element 0x4: Temperature sensors OK (Status=ok (bytes=0x01 0x00 0x32 0x00)) Element 0x5: Enclosure OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) Element 0x6: Audible alarm OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) YAY! So now three questions: 1. Does anybody else have alike hardware and wish to test it? 2. Patch reviews are welcome. 3. Is there any software except share/examples/ses working with ses(4) and/or some good use practices? -- Alexander Motin From owner-freebsd-scsi@FreeBSD.ORG Fri May 27 07:19:43 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFE7F106566B; Fri, 27 May 2011 07:19:43 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe04.c2i.net [212.247.154.98]) by mx1.freebsd.org (Postfix) with ESMTP id 295D48FC08; Fri, 27 May 2011 07:19:42 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=wd7fLirDSts22yawIUsTeMUS9lsm8Llc0grT6RvpTjU= c=1 sm=1 a=SvYTsOw2Z4kA:10 a=gH2l33NO9zgA:10 a=I_V-8a3mpGgA:10 a=WQU8e4WWZSUA:10 a=Fdkxr_5KmFUA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=VrpS9D41Wf-qsKqnjl0A:9 a=pvA44qeTxYYA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe04.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 131894313; Fri, 27 May 2011 09:09:39 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Fri, 27 May 2011 09:08:23 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; ) References: <4DDF4C23.3010600@FreeBSD.org> In-Reply-To: <4DDF4C23.3010600@FreeBSD.org> X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq, NwSZ4V"|LR.+tj}g5 %V,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( :AuzV9:.hESm-x4h240C`9=w MIME-Version: 1.0 Content-Type: Text/Plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Message-Id: <201105270908.23256.hselasky@c2i.net> Cc: freebsd-scsi@freebsd.org, Alexander Motin , freebsd-hardware@freebsd.org Subject: Re: SES/SAF-TE + SATA == SEMB! X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2011 07:19:43 -0000 On Friday 27 May 2011 09:00:51 Alexander Motin wrote: > YAY! > > So now three questions: > 1. Does anybody else have alike hardware and wish to test it? > 2. Patch reviews are welcome. > 3. Is there any software except share/examples/ses working with ses(4) > and/or some good use practices? Does it work with USB? --HPS From owner-freebsd-scsi@FreeBSD.ORG Fri May 27 07:24:25 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E980E106566C; Fri, 27 May 2011 07:24:25 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 14C178FC1B; Fri, 27 May 2011 07:24:24 +0000 (UTC) Received: by fxm11 with SMTP id 11so1646762fxm.13 for ; Fri, 27 May 2011 00:24:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=PkTq5FUfZTAypxV5eMr8JzzH23KUe0nLqNVlRDrqYEw=; b=ocX5Jlf8Ipv3VYn3GEa4/bZOfn+Ur6XKX3BXuMfwqBDJBxdcnMrAFOddnWq7JpLVaT 9ttNhiisfWVw4Kgvk0YNudG4n+gK3BHKUg1EpTpQmKoTdlM0gN4GXjHqo7qEn1M38cSW N8ziNnWlXmyMPp/y72BGSeGUHtqulHT+8dQ08= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=untyCX1EbpXc+/NZemcYHvYjOqwo+yK0bkNf7eLFoxXEYQDVerH9tzQ9M0H5V43W3W IOQ46hboRptvuV0/I+73MXxXbFleW/w/mvleD22uDU5YV7XfoG7bLFbX2E6869KWxmZm +FSVfc2+F2Ez6cqJjuxYGydotL4Lagg5ttmGs= Received: by 10.223.28.220 with SMTP id n28mr514106fac.101.1306481063880; Fri, 27 May 2011 00:24:23 -0700 (PDT) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id x15sm560722fah.22.2011.05.27.00.24.22 (version=SSLv3 cipher=OTHER); Fri, 27 May 2011 00:24:23 -0700 (PDT) Sender: Alexander Motin Message-ID: <4DDF518A.2070901@FreeBSD.org> Date: Fri, 27 May 2011 10:23:54 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Hans Petter Selasky References: <4DDF4C23.3010600@FreeBSD.org> <201105270908.23256.hselasky@c2i.net> In-Reply-To: <201105270908.23256.hselasky@c2i.net> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: SES/SAF-TE + SATA == SEMB! X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2011 07:24:26 -0000 Hans Petter Selasky wrote: > On Friday 27 May 2011 09:00:51 Alexander Motin wrote: >> YAY! >> >> So now three questions: >> 1. Does anybody else have alike hardware and wish to test it? >> 2. Patch reviews are welcome. >> 3. Is there any software except share/examples/ses working with ses(4) >> and/or some good use practices? > > Does it work with USB? SEMB is ATA-specific. I've never heard about SES/SAF-TE on USB, but I think more likely it will be reported as usual SCSI Enclosure Services device -- there is no need to invent something new. Technically for ATA it also could be made as regular ATAPI (SCSI) device, but for some reason it was made in custom way. -- Alexander Motin From owner-freebsd-scsi@FreeBSD.ORG Fri May 27 13:40:10 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E37C71065675 for ; Fri, 27 May 2011 13:40:09 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 9E8588FC12 for ; Fri, 27 May 2011 13:40:09 +0000 (UTC) Received: from [192.168.135.104] (c-76-126-155-117.hsd1.ca.comcast.net [76.126.155.117]) (authenticated bits=0) by ns1.feral.com (8.14.4/8.14.4) with ESMTP id p4RDe6Ph097523 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Fri, 27 May 2011 06:40:08 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <4DDFA9B7.5000904@feral.com> Date: Fri, 27 May 2011 06:40:07 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <4DDF4C23.3010600@FreeBSD.org> In-Reply-To: <4DDF4C23.3010600@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (ns1.feral.com [192.67.166.1]); Fri, 27 May 2011 06:40:08 -0700 (PDT) Subject: Re: SES/SAF-TE + SATA == SEMB! X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2011 13:40:10 -0000 Awesome dude! On 5/27/2011 12:00 AM, Alexander Motin wrote: > Hi. > > As probably not many know, SATA specification defines the way to talk to > SES/SAF-TE enclosures -- Serial ATA Enclosure Management Bridge (SEMB). > It can be either separate device or built-in to SATA Port Multiplier. I > know at leat two models of Port Multipliers including SEMB and having > I2C interfaces to talk to SEP (backplane): SiI3726 and SiI4726. > Unluckily such combination of hardware is not widely spread (backplanes > are rarely used in desktops, while PMPs are rarely used in servers), but > finally I've built such setup! I've connected SuperMicro SAS815TQ > backplane to the SiI3726 multiplier with I2C cable and it works like a > charm! > > I've made a patch for HEAD to support it. It adds SEMB devices support > to the ATA/SATA XPT probe code, some glue to handle one more ATA-based > command protocol and some changes to ses(4) driver to teach it talk to > such devices: > http://people.freebsd.org/~mav/semb.patch > > As result I've got: > > %dmesg |grep ses0 > ses0 at ahcich8 bus 0 scbus8 target 5 lun 0 > ses0: SEMB S-E-S 2.00 device > ses0: Serial Number 50030481 > ses0: 150.000MB/s transfers (SATA 1.x, NONE, PIO 8192bytes) > ses0: SEMB SES Device > ses0: GenCode 0 0 Subenclosures > ses0: SubEnclosure ID 0, 4 Types With this ID, Enclosure Length 36 > ses0: WWN: 3530303330343831 > ses0: Type Desc[0]: Type 0x17, MaxElt 4, In Subenc 0, Text Length 0 > ses0: Type Desc[1]: Type 0x4, MaxElt 1, In Subenc 0, Text Length 0 > ses0: Type Desc[2]: Type 0xe, MaxElt 1, In Subenc 0, Text Length 0 > ses0: Type Desc[3]: Type 0x6, MaxElt 1, In Subenc 0, Text Length 0 > > %camcontrol devlist > at scbus8 target 0 lun 0 (ada0,pass1) > at scbus8 target 1 lun 0 (ada1,pass2) > at scbus8 target 2 lun 0 (pass5,ada2) > at scbus8 target 3 lun 0 (pass6,ada3) > at scbus8 target 5 lun 0 (ses0,pass3) > at scbus8 target 15 lun 0 (pass4,pmp0) > > %getencstat -v /dev/ses0 > /dev/ses0: Enclosure Status > Element 0x0: Array device OK (Status=ok (bytes=0x11 0x00 0x00 0x00)) > Element 0x1: Array device OK (Status=ok (bytes=0x11 0x00 0x00 0x00)) > Element 0x2: Array device OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) > Element 0x3: Array device OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) > Element 0x4: Temperature sensors OK (Status=ok (bytes=0x01 0x00 0x32 0x00)) > Element 0x5: Enclosure OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) > Element 0x6: Audible alarm OK (Status=ok (bytes=0x01 0x00 0x00 0x00)) > > YAY! > > So now three questions: > 1. Does anybody else have alike hardware and wish to test it? > 2. Patch reviews are welcome. > 3. Is there any software except share/examples/ses working with ses(4) > and/or some good use practices? > From owner-freebsd-scsi@FreeBSD.ORG Sat May 28 22:03:44 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C06B61065670 for ; Sat, 28 May 2011 22:03:44 +0000 (UTC) (envelope-from dan@langille.org) Received: from nyi.unixathome.org (nyi.unixathome.org [64.147.113.42]) by mx1.freebsd.org (Postfix) with ESMTP id 963A98FC0A for ; Sat, 28 May 2011 22:03:44 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id B249050893 for ; Sat, 28 May 2011 23:03:43 +0100 (BST) X-Virus-Scanned: amavisd-new at unixathome.org Received: from nyi.unixathome.org ([127.0.0.1]) by localhost (nyi.unixathome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 97KEYbQiMPlo for ; Sat, 28 May 2011 23:03:43 +0100 (BST) Received: from smtp-auth.unixathome.org (smtp-auth.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) by nyi.unixathome.org (Postfix) with ESMTPSA id 53DDA50882 for ; Sat, 28 May 2011 23:03:43 +0100 (BST) From: Dan Langille Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sat, 28 May 2011 18:03:41 -0400 Message-Id: To: freebsd-scsi@freebsd.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: Does the tape library need cleaning? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2011 22:03:44 -0000 I'm wondering if there is a way to query my tape library to see if = cleaning is required? This information is shown on the display of the = unit, but I'd like to query the device and display it on a webpage. Here is what I have. $ mtx -f /dev/pass11 inquiry Product Type: Medium Changer Vendor ID: 'DEC ' Product ID: 'TL800 (C) DEC' Revision: '0326' Attached Changer API: No I'm guessing I need to know more about about the scsi commands I can = send to the device and use camcontrol to extract the information. Much = like this command pulls back data (as extracted from a a: set -- `camcontrol cmd $tape -v -t 3 -c "4d 0 43 0 0 0 0 0 40 0" -i 64 = \ "{skip} *i4 \ {skip} *i4 \ {Corrected errors with substantial delay } i4 \ {skip} *i4 \ {Corrected errors with possible delay } i4 \ {skip} *i4 \ {Total errors } i4 \ {skip} *i4 \ {Total errors corrected } i4 \ {skip} *i4 \ {Total times correction algorithm processed} i4 \ {skip} *i4 \ {Total bytes processed } i2 i3 i3 \ {skip} *i4 \ {Total uncorrected errors } i4" ` echo " Corrected errors with substantial delay: $1" echo " Corrected errors with possible delay : $2" echo " Total errors : $3" echo " Total errors corrected : $4" echo " Total times correction algorithm used : $5" tmp=3D`echo "($6 * 16777216 + $7) * 16777216 + $8" | bc` echo " Total bytes processed : $tmp" --=20 Dan Langille - http://langille.org