From owner-freebsd-scsi@FreeBSD.ORG Sun Apr 11 08:36:20 2010 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 CCD4E106564A; Sun, 11 Apr 2010 08:36:20 +0000 (UTC) (envelope-from uqs@spoerlein.net) Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2001:470:9a47::1]) by mx1.freebsd.org (Postfix) with ESMTP id 87AA38FC12; Sun, 11 Apr 2010 08:36:20 +0000 (UTC) Received: from acme.spoerlein.net (localhost.spoerlein.net [IPv6:::1]) by acme.spoerlein.net (Postfix) with ESMTPS id C0B435C59; Sun, 11 Apr 2010 10:36:19 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=spoerlein.net; s=dkim200908; t=1270974979; bh=94OmU0a0wHfv+irZ7HPSwj0t93YMKKl3XBwsr0gWXG8=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:In-Reply-To; b=qwkvigfVq4bRdrZbUdU8la6xFRugKQFj0rw9iYO51/gmdvWmNlcaDfUGLHaAJqJ4q bd6X7D/ego1tX6zXZnirLbXXyKF23DWVhlp7DpWG6D+MNsZeCwgEph1PAsomfM9CGU pbjehxik2Gm5a2WGf9B9W/qXlUyCkVwk1u0fbnOk= Received: (from uqs@localhost) by acme.spoerlein.net (8.14.4/8.14.4/Submit) id o3B8aJQS057712; Sun, 11 Apr 2010 10:36:19 +0200 (CEST) (envelope-from uqs@spoerlein.net) Date: Sun, 11 Apr 2010 10:36:19 +0200 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: Andriy Gapon Message-ID: <20100411083618.GA57638@acme.spoerlein.net> Mail-Followup-To: Andriy Gapon , Pavel Sukhoy , freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org, Markus Wild , Hans Petter Selasky References: <903d65bf1d5624b5208c588b21e679ea@ripn.net> <4BBCFE30.2010709@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BBCFE30.2010709@icyb.net.ua> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-scsi@freebsd.org, Hans Petter Selasky , Markus Wild , freebsd-hackers@freebsd.org Subject: Re: virtual drive errors 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: Sun, 11 Apr 2010 08:36:20 -0000 On Thu, 08.04.2010 at 00:50:40 +0300, Andriy Gapon wrote: > Looking at cdcheckmedia and at the logged READ TOC (0x43) SCSI command errors > (as reported by Markus) I see the following problem. Even if cdsize() call at > the beginning of cdcheckmedia() succeeds, a subsequent failure of cdreadtoc() > throws us to 'bailout' label which is past the code that sets d_mediasize. > > I think that the following patch should help with this situation (and possibly > other cases with READ TOC problems): > > --- a/sys/cam/scsi/scsi_cd.c > +++ b/sys/cam/scsi/scsi_cd.c >[snip] This patch, much like the one in kern/138789 makes my external Plextor PX-755A drive successfully read "mastered" DVD media, i.e., the retail kind, not DVD-R/RW. So, please commit some version of this patch. Thanks! Regards, Uli From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 12 03:40:29 2010 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 56278106564A for ; Mon, 12 Apr 2010 03:40:29 +0000 (UTC) (envelope-from brad@wcubed.net) Received: from mail.datausa.com (mail.datausa.com [216.150.220.220]) by mx1.freebsd.org (Postfix) with SMTP id 2F0658FC1A for ; Mon, 12 Apr 2010 03:40:28 +0000 (UTC) Received: (qmail 27698 invoked by uid 89); 11 Apr 2010 20:09:56 -0600 Received: from c-76-25-180-188.hsd1.co.comcast.net (HELO ?10.0.1.1?) (brad@wcubed.net@76.25.180.188) by mail.datausa.com with SMTP; 11 Apr 2010 20:09:56 -0600 Message-ID: <4BC280EE.5090202@wcubed.net> Date: Sun, 11 Apr 2010 20:09:50 -0600 From: Brad Waite User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081209 Lightning/0.9 Thunderbird/2.0.0.19 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: 4BBF720A.3020300@wcubed.net X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: QLogic 2360 FC HBAs not playing well with others 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, 12 Apr 2010 03:40:29 -0000 > > Matthew Jacob wrote: > >> On 04/09/2010 11:29 AM, Brad Waite wrote: > >> I beseech you, oh great masters of SCSI and fibre channel, hear my > pleas > >> for help! > >> > >> My 2 QLE2360s don't appear to be waking up properly in a Dell R710 > >> running 7.2 AMD64. At the very least, they're not recognizing any of > >> the volumes on the Sun 2540 array in the fabric. Everything works just > >> fine under VMware ESXi 4.1, though. > >> > > > > Get newer firmware either by upgrading with RELENG_7 or snagging > > asm_2300.h from RELENG_7 and rebuilding. > > > > You don't have to load all of ispfw > > > > isp2300_LOAD=YES > > > > should get you just that onemodule > > > > the latest in the FreeBSD tree is 3.03.26 > > Woot. That helped. Built & installed RELENG_7, but I've got some > more wierdness. Woot. That helped. Built & installed RELENG_7, but I've got some more wierdness. First off I've got da0 - da15 showing similar to this: da0 at isp0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device da0: 200.000MB/s transfers da0: Command Queueing Enabled da0: 138989MB (284650656 512 byte sectors: 255H 63S/T 17718C) We've got a Sun Storagetek 2540 12-drive array with 4 volumes mapped to this host. It would appear that it's showing the 4 volumes AND each of the 12 drives. Is that normal? Next, I have about 20 of the following errors for each of da1, da2, da3, da4, da9, da10, da11 & da12. (da1:isp0:0:0:1): READ(6)/WRITE(6) not supported, increasing minimum_cmd_size to 10. (da1:isp0:0:0:1): READ(10). CDB: 28 0 0 0 0 0 0 0 1 0 (da1:isp0:0:0:1): CAM Status: SCSI Status Error (da1:isp0:0:0:1): SCSI Status: Check Condition (da1:isp0:0:0:1): ILLEGAL REQUEST asc:94,1 (da1:isp0:0:0:1): Vendor Specific ASC (da1:isp0:0:0:1): Unretryable error What's going on here? Is there any config I need to to for volume mapping and/or multipathing? I'm a complete newb when it comes to FC on FreeBSD, so forgive my ignorance. Thanks for the help, guys! From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 12 03:49:55 2010 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 5E4A7106564A for ; Mon, 12 Apr 2010 03:49:55 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id 34EBF8FC18 for ; Mon, 12 Apr 2010 03:49:55 +0000 (UTC) Received: from gjp by noop.in-addr.com with local (Exim 4.54 (FreeBSD)) id 1O1AeX-000Amj-PN; Sun, 11 Apr 2010 23:49:37 -0400 Date: Sun, 11 Apr 2010 23:49:37 -0400 From: Gary Palmer To: Brad Waite Message-ID: <20100412034937.GA24680@in-addr.com> References: <4BC280EE.5090202@wcubed.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BC280EE.5090202@wcubed.net> Cc: freebsd-scsi@freebsd.org Subject: Re: QLogic 2360 FC HBAs not playing well with others 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, 12 Apr 2010 03:49:55 -0000 On Sun, Apr 11, 2010 at 08:09:50PM -0600, Brad Waite wrote: > > > Matthew Jacob wrote: > > >> On 04/09/2010 11:29 AM, Brad Waite wrote: > > >> I beseech you, oh great masters of SCSI and fibre channel, hear my > > pleas > > >> for help! > > >> > > >> My 2 QLE2360s don't appear to be waking up properly in a Dell R710 > > >> running 7.2 AMD64. At the very least, they're not recognizing any of > > >> the volumes on the Sun 2540 array in the fabric. Everything works just > > >> fine under VMware ESXi 4.1, though. > > >> > > > > > > Get newer firmware either by upgrading with RELENG_7 or snagging > > > asm_2300.h from RELENG_7 and rebuilding. > > > > > > You don't have to load all of ispfw > > > > > > isp2300_LOAD=YES > > > > > > should get you just that onemodule > > > > > > the latest in the FreeBSD tree is 3.03.26 > > > > Woot. That helped. Built & installed RELENG_7, but I've got some > > more wierdness. > > Woot. That helped. > > Built & installed RELENG_7, but I've got some more wierdness. > > First off I've got da0 - da15 showing similar to this: > > da0 at isp0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-5 device > da0: 200.000MB/s transfers > da0: Command Queueing Enabled > da0: 138989MB (284650656 512 byte sectors: 255H 63S/T 17718C) > > We've got a Sun Storagetek 2540 12-drive array with 4 volumes mapped to > this host. It would appear that it's showing the 4 volumes AND each of > the 12 drives. Is that normal? > > Next, I have about 20 of the following errors for each of da1, da2, da3, > da4, da9, da10, da11 & da12. > > (da1:isp0:0:0:1): READ(6)/WRITE(6) not supported, increasing > minimum_cmd_size to 10. > (da1:isp0:0:0:1): READ(10). CDB: 28 0 0 0 0 0 0 0 1 0 > (da1:isp0:0:0:1): CAM Status: SCSI Status Error > (da1:isp0:0:0:1): SCSI Status: Check Condition > (da1:isp0:0:0:1): ILLEGAL REQUEST asc:94,1 > (da1:isp0:0:0:1): Vendor Specific ASC > (da1:isp0:0:0:1): Unretryable error > > What's going on here? > > Is there any config I need to to for volume mapping and/or > multipathing? I'm a complete newb when it comes to FC on FreeBSD, so > forgive my ignorance. > > Thanks for the help, guys! I suspect the reason you have 16 disk devices showing up is that you are running multipath. You will get one da device showing up for each different path, and if you're running a full multipath environment that's likely 4 paths per device, which would lead to the 16 disks (unless they're not the sizes you expect, but I would tend to suspect its a multipath artifact) To handle multipath you probably want to look at gmultipath(8). I'm not sure about READ/WRITE errors. You say they show up for 8 devices? Is it possible that the array is not true active/active on the controllers? Its possible that half the paths are going to a controller that is rejecting the I/O until the LUN fails over, but thats just a guess based on the error message. If you can look at the controller/bus/target/lun information from dmesg and see if you can spot a pattern about the path to the LUNs giving the error that may give a better idea about whats going on. Regards, Gary From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 12 11:07:09 2010 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 6CC051065688 for ; Mon, 12 Apr 2010 11:07:09 +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 517B48FC16 for ; Mon, 12 Apr 2010 11:07:09 +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 o3CB791Q042560 for ; Mon, 12 Apr 2010 11:07:09 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o3CB78E8042558 for freebsd-scsi@FreeBSD.org; Mon, 12 Apr 2010 11:07:08 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 12 Apr 2010 11:07:08 GMT Message-Id: <201004121107.o3CB78E8042558@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, 12 Apr 2010 11:07:09 -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/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 p kern/130735 scsi [cam] [patch] pass M_NOWAIT to the malloc() call insid 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/124667 scsi [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi o kern/123674 scsi [ahc] ahc driver dumping f kern/123666 scsi [aac] attach fails with Adaptec SAS RAID 3805 controll 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/119668 scsi [cam] [patch] certain errors are too verbose comparing 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/94838 scsi Kernel panic while mounting SD card with lock switch o 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 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/40895 scsi wierd kernel / device driver bug 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 37 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 12 17:03:24 2010 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 AD9781065674 for ; Mon, 12 Apr 2010 17:03:24 +0000 (UTC) (envelope-from westr@connection.ca) Received: from nc-tor-mail2.connection.ca (nc-tor-mail2.connection.ca [205.207.122.27]) by mx1.freebsd.org (Postfix) with ESMTP id 8E31C8FC13 for ; Mon, 12 Apr 2010 17:03:24 +0000 (UTC) Received: from westr-main.tor.connection.ca (external.tor.connection.ca [216.234.38.18]) by nc-tor-mail2.connection.ca (Postfix) with ESMTP id CD1CD74E55A for ; Mon, 12 Apr 2010 13:03:23 -0400 (EDT) Date: Mon, 12 Apr 2010 13:03:23 -0400 From: Ross Organization: Network Connection X-Priority: 3 (Normal) Message-ID: <223938752.20100412130323@connection.ca> To: freebsd-scsi@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: isp driver - sysctl controls missing X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ross List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Apr 2010 17:03:24 -0000 It looks like in the isp(4) driver update that happened back when Freebsd v8.0 got updated, it looks like the user-modifiable sysctls got removed and timeouts are now hardcoded. The man page for isp state: -= SYSCTL OPTIONS dev.isp.N.loop_down_limit This value says how long to wait in seconds after loop has gone down before giving up and expiring all of the devices that were visible. The default is 300 seconds (5 minutes). A seperate (nonadjustable) timeout is used when booting to not stop booting on lack of FC connectivity. dev.isp.N.gone_device_time This value says how long to wait for devices to reappear if they (temporarily) disappear due to loop or fabric events. While this timeout is running, I/O to those devices will simply be held. -= But checking over the driver code shows sysctl details are now removed and the hardcoded value for loop_down_limit is now 60 seconds and gone_device_time is 30 seconds. Anyone know if there's any reason for the sysctl is being pulled out, and the limits being so high? We use this in conjunction with geom multipath, so would prefer to fail over to another fc path asap when there's an issue. Cheers, Ross. -- From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 12 17:06:24 2010 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 CB94D1065676 for ; Mon, 12 Apr 2010 17:06:24 +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 992AF8FC1E for ; Mon, 12 Apr 2010 17:06:24 +0000 (UTC) Received: from [192.168.221.2] (remotevpn [192.168.221.2]) by ns1.feral.com (8.14.3/8.14.3) with ESMTP id o3CH6Hfl057380 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 12 Apr 2010 10:06:20 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <4BC35309.1010807@feral.com> Date: Mon, 12 Apr 2010 10:06:17 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc11 Thunderbird/3.0.4 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <223938752.20100412130323@connection.ca> In-Reply-To: <223938752.20100412130323@connection.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.2.3 (ns1.feral.com [192.168.221.1]); Mon, 12 Apr 2010 10:06:20 -0700 (PDT) Subject: Re: isp driver - sysctl controls missing 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, 12 Apr 2010 17:06:24 -0000 On 04/12/2010 10:03 AM, Ross wrote: > It looks like in the isp(4) driver update that happened back when Freebsd > v8.0 got updated, it looks like the user-modifiable sysctls got > removed and timeouts are now hardcoded. > > The man page for isp state: > -= > SYSCTL OPTIONS > dev.isp.N.loop_down_limit > This value says how long to wait in seconds after loop has gone > down before giving up and expiring all of the devices that were > visible. The default is 300 seconds (5 minutes). A seperate > (nonadjustable) timeout is used when booting to not stop booting > on lack of FC connectivity. > > dev.isp.N.gone_device_time > This value says how long to wait for devices to reappear if they > (temporarily) disappear due to loop or fabric events. While this > timeout is running, I/O to those devices will simply be held. > > -= > > But checking over the driver code shows sysctl details are now removed > and the hardcoded value for loop_down_limit is now 60 seconds and > gone_device_time is 30 seconds. > > Anyone know if there's any reason for the sysctl is being pulled out, > and the limits being so high? We use this in conjunction with geom > multipath, so would prefer to fail over to another fc path asap when > there's an issue. > > > Cheers, > Ross. > > Sounds like a bug that I need to fix. From owner-freebsd-scsi@FreeBSD.ORG Tue Apr 13 16:49:20 2010 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 6FE1F1065679 for ; Tue, 13 Apr 2010 16:49:20 +0000 (UTC) (envelope-from freebsd@wcubed.net) Received: from mail.datausa.com (mail.datausa.com [216.150.220.220]) by mx1.freebsd.org (Postfix) with SMTP id 3F8358FC28 for ; Tue, 13 Apr 2010 16:49:20 +0000 (UTC) Received: (qmail 18404 invoked by uid 89); 13 Apr 2010 10:49:16 -0600 Received: from c-76-25-180-188.hsd1.co.comcast.net (HELO ?10.0.1.1?) (brad@wcubed.net@76.25.180.188) by mail.datausa.com with SMTP; 13 Apr 2010 10:49:16 -0600 Message-ID: <4BC4A084.7050906@wcubed.net> Date: Tue, 13 Apr 2010 10:49:08 -0600 From: Brad Waite User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081209 Lightning/0.9 Thunderbird/2.0.0.19 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: Gary Palmer References: <4BC280EE.5090202@wcubed.net> <20100412034937.GA24680@in-addr.com> In-Reply-To: <20100412034937.GA24680@in-addr.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-scsi@freebsd.org Subject: Re: QLogic 2360 FC HBAs not playing well with others 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, 13 Apr 2010 16:49:20 -0000 Gary Palmer wrote: > On Sun, Apr 11, 2010 at 08:09:50PM -0600, Brad Waite wrote: >>>> Matthew Jacob wrote: >>>>> On 04/09/2010 11:29 AM, Brad Waite wrote: >>>>> I beseech you, oh great masters of SCSI and fibre channel, hear my >>> pleas >>>>> for help! >>>>> >>>>> My 2 QLE2360s don't appear to be waking up properly in a Dell R710 >>>>> running 7.2 AMD64. At the very least, they're not recognizing any of >>>>> the volumes on the Sun 2540 array in the fabric. Everything works just >>>>> fine under VMware ESXi 4.1, though. >>>>> >>>> Get newer firmware either by upgrading with RELENG_7 or snagging >>>> asm_2300.h from RELENG_7 and rebuilding. >>>> >>>> You don't have to load all of ispfw >>>> >>>> isp2300_LOAD=YES >>>> >>>> should get you just that onemodule >>>> >>>> the latest in the FreeBSD tree is 3.03.26 >>> Woot. That helped. Built & installed RELENG_7, but I've got some >>> more wierdness. >> Woot. That helped. >> >> Built & installed RELENG_7, but I've got some more wierdness. >> >> First off I've got da0 - da15 showing similar to this: >> >> da0 at isp0 bus 0 target 0 lun 0 >> da0: Fixed Direct Access SCSI-5 device >> da0: 200.000MB/s transfers >> da0: Command Queueing Enabled >> da0: 138989MB (284650656 512 byte sectors: 255H 63S/T 17718C) >> >> We've got a Sun Storagetek 2540 12-drive array with 4 volumes mapped to >> this host. It would appear that it's showing the 4 volumes AND each of >> the 12 drives. Is that normal? >> >> Next, I have about 20 of the following errors for each of da1, da2, da3, >> da4, da9, da10, da11 & da12. >> >> (da1:isp0:0:0:1): READ(6)/WRITE(6) not supported, increasing >> minimum_cmd_size to 10. >> (da1:isp0:0:0:1): READ(10). CDB: 28 0 0 0 0 0 0 0 1 0 >> (da1:isp0:0:0:1): CAM Status: SCSI Status Error >> (da1:isp0:0:0:1): SCSI Status: Check Condition >> (da1:isp0:0:0:1): ILLEGAL REQUEST asc:94,1 >> (da1:isp0:0:0:1): Vendor Specific ASC >> (da1:isp0:0:0:1): Unretryable error >> >> What's going on here? >> >> Is there any config I need to to for volume mapping and/or >> multipathing? I'm a complete newb when it comes to FC on FreeBSD, so >> forgive my ignorance. >> >> Thanks for the help, guys! > > I suspect the reason you have 16 disk devices showing up is that you > are running multipath. You will get one da device showing up for each > different path, and if you're running a full multipath environment > that's likely 4 paths per device, which would lead to the 16 disks > (unless they're not the sizes you expect, but I would tend to suspect > its a multipath artifact) Thanks for pointing out what should have been obvious. The Sun 2540 has 2 ports on 2 controllers and camcontrol shows exactly that: # camcontrol devlist at scbus0 target 0 lun 0 (da0,pass0) at scbus0 target 0 lun 1 (da1,pass1) at scbus0 target 0 lun 2 (da2,pass2) at scbus0 target 0 lun 3 (da3,pass3) at scbus0 target 1 lun 0 (da4,pass4) at scbus0 target 1 lun 1 (da5,pass5) at scbus0 target 1 lun 2 (da6,pass6) at scbus0 target 1 lun 3 (da7,pass7) at scbus1 target 0 lun 0 (da8,pass8) at scbus1 target 0 lun 1 (da9,pass9) at scbus1 target 0 lun 2 (da10,pass10) at scbus1 target 0 lun 3 (da11,pass11) at scbus1 target 1 lun 0 (da12,pass12) at scbus1 target 1 lun 1 (da13,pass13) at scbus1 target 1 lun 2 (da14,pass14) at scbus1 target 1 lun 3 (da15,pass15) > To handle multipath you probably want to look at gmultipath(8). > > I'm not sure about READ/WRITE errors. You say they show up for 8 > devices? Is it possible that the array is not true active/active > on the controllers? Its possible that half the paths are going to > a controller that is rejecting the I/O until the LUN fails over, > but thats just a guess based on the error message. If you can > look at the controller/bus/target/lun information from dmesg and > see if you can spot a pattern about the path to the LUNs giving > the error that may give a better idea about whats going on. I think you've nailed it. da4-7 & da12-15 have the following respective lines in dmesg: da[4-7]: 200.000MB/s transfers WWNN 0x200400a0b8388efd WWPN 0x203500a0b8388efd PortID 0x10100 da[12-15]: 200.000MB/s transfers WWNN 0x200400a0b8388efd WWPN 0x202500a0b8388efd PortID 0x10100 The two WWPNs correspond to the 2540's controllers and the write errors are on da0-3 & da8-11. I can't find anything yet in the docs on making the other ports active, but I successfully labeled da7 & da15 with gmultipath, although I couldn't add da3 & da11 due to write errors. No real surprise, but since I can't add the label, what happens if one of the active ports on a controller fails? I know I'd have the other path to the active port on the other controller, but would I have to manually add the label to the volumes from newly-active port? From owner-freebsd-scsi@FreeBSD.ORG Tue Apr 13 16:53:51 2010 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 F3F0A106566B for ; Tue, 13 Apr 2010 16:53:50 +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 828848FC0C for ; Tue, 13 Apr 2010 16:53:50 +0000 (UTC) Received: from [192.168.221.2] (remotevpn [192.168.221.2]) by ns1.feral.com (8.14.3/8.14.3) with ESMTP id o3DGrnSk041586 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 13 Apr 2010 09:53:50 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <4BC4A19D.2080005@feral.com> Date: Tue, 13 Apr 2010 09:53:49 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc11 Thunderbird/3.0.4 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <4BC280EE.5090202@wcubed.net> <20100412034937.GA24680@in-addr.com> <4BC4A084.7050906@wcubed.net> In-Reply-To: <4BC4A084.7050906@wcubed.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.2.3 (ns1.feral.com [192.168.221.1]); Tue, 13 Apr 2010 09:53:50 -0700 (PDT) Subject: Re: QLogic 2360 FC HBAs not playing well with others 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, 13 Apr 2010 16:53:51 -0000 On 04/13/2010 09:49 AM, Brad Waite wrote: > Gary Palmer wrote: > >> On Sun, Apr 11, 2010 at 08:09:50PM -0600, Brad Waite wrote: >> >>>>> Matthew Jacob wrote: >>>>> >>>>>> On 04/09/2010 11:29 AM, Brad Waite wrote: >>>>>> I beseech you, oh great masters of SCSI and fibre channel, hear my >>>>>> >>>> pleas >>>> >>>>>> for help! >>>>>> >>>>>> My 2 QLE2360s don't appear to be waking up properly in a Dell R710 >>>>>> running 7.2 AMD64. At the very least, they're not recognizing any of >>>>>> the volumes on the Sun 2540 array in the fabric. Everything works just >>>>>> fine under VMware ESXi 4.1, though. >>>>>> >>>>>> >>>>> Get newer firmware either by upgrading with RELENG_7 or snagging >>>>> asm_2300.h from RELENG_7 and rebuilding. >>>>> >>>>> You don't have to load all of ispfw >>>>> >>>>> isp2300_LOAD=YES >>>>> >>>>> should get you just that onemodule >>>>> >>>>> the latest in the FreeBSD tree is 3.03.26 >>>>> >>>> Woot. That helped. Built& installed RELENG_7, but I've got some >>>> more wierdness. >>>> >>> Woot. That helped. >>> >>> Built& installed RELENG_7, but I've got some more wierdness. >>> >>> First off I've got da0 - da15 showing similar to this: >>> >>> da0 at isp0 bus 0 target 0 lun 0 >>> da0: Fixed Direct Access SCSI-5 device >>> da0: 200.000MB/s transfers >>> da0: Command Queueing Enabled >>> da0: 138989MB (284650656 512 byte sectors: 255H 63S/T 17718C) >>> >>> We've got a Sun Storagetek 2540 12-drive array with 4 volumes mapped to >>> this host. It would appear that it's showing the 4 volumes AND each of >>> the 12 drives. Is that normal? >>> >>> Next, I have about 20 of the following errors for each of da1, da2, da3, >>> da4, da9, da10, da11& da12. >>> >>> (da1:isp0:0:0:1): READ(6)/WRITE(6) not supported, increasing >>> minimum_cmd_size to 10. >>> (da1:isp0:0:0:1): READ(10). CDB: 28 0 0 0 0 0 0 0 1 0 >>> (da1:isp0:0:0:1): CAM Status: SCSI Status Error >>> (da1:isp0:0:0:1): SCSI Status: Check Condition >>> (da1:isp0:0:0:1): ILLEGAL REQUEST asc:94,1 >>> (da1:isp0:0:0:1): Vendor Specific ASC >>> (da1:isp0:0:0:1): Unretryable error >>> >>> What's going on here? >>> >>> Is there any config I need to to for volume mapping and/or >>> multipathing? I'm a complete newb when it comes to FC on FreeBSD, so >>> forgive my ignorance. >>> >>> Thanks for the help, guys! >>> >> I suspect the reason you have 16 disk devices showing up is that you >> are running multipath. You will get one da device showing up for each >> different path, and if you're running a full multipath environment >> that's likely 4 paths per device, which would lead to the 16 disks >> (unless they're not the sizes you expect, but I would tend to suspect >> its a multipath artifact) >> > Thanks for pointing out what should have been obvious. The Sun 2540 has 2 ports on 2 controllers and camcontrol shows > exactly that: > > # camcontrol devlist > at scbus0 target 0 lun 0 (da0,pass0) > at scbus0 target 0 lun 1 (da1,pass1) > at scbus0 target 0 lun 2 (da2,pass2) > at scbus0 target 0 lun 3 (da3,pass3) > at scbus0 target 1 lun 0 (da4,pass4) > at scbus0 target 1 lun 1 (da5,pass5) > at scbus0 target 1 lun 2 (da6,pass6) > at scbus0 target 1 lun 3 (da7,pass7) > at scbus1 target 0 lun 0 (da8,pass8) > at scbus1 target 0 lun 1 (da9,pass9) > at scbus1 target 0 lun 2 (da10,pass10) > at scbus1 target 0 lun 3 (da11,pass11) > at scbus1 target 1 lun 0 (da12,pass12) > at scbus1 target 1 lun 1 (da13,pass13) > at scbus1 target 1 lun 2 (da14,pass14) > at scbus1 target 1 lun 3 (da15,pass15) > > >> To handle multipath you probably want to look at gmultipath(8). >> >> I'm not sure about READ/WRITE errors. You say they show up for 8 >> devices? Is it possible that the array is not true active/active >> on the controllers? Its possible that half the paths are going to >> a controller that is rejecting the I/O until the LUN fails over, >> but thats just a guess based on the error message. If you can >> look at the controller/bus/target/lun information from dmesg and >> see if you can spot a pattern about the path to the LUNs giving >> the error that may give a better idea about whats going on. >> > I think you've nailed it. da4-7& da12-15 have the following respective lines in dmesg: > > da[4-7]: 200.000MB/s transfers WWNN 0x200400a0b8388efd WWPN 0x203500a0b8388efd PortID 0x10100 > da[12-15]: 200.000MB/s transfers WWNN 0x200400a0b8388efd WWPN 0x202500a0b8388efd PortID 0x10100 > > The two WWPNs correspond to the 2540's controllers and the write errors are on da0-3& da8-11. I can't find anything > yet in the docs on making the other ports active, but > > I successfully labeled da7& da15 with gmultipath, although I couldn't add da3& da11 due to write errors. No real > surprise, but since I can't add the label, what happens if one of the active ports on a controller fails? I know I'd > have the other path to the active port on the other controller, but would I have to manually add the label to the > volumes from newly-active port? > There's only one spindle. The label is on it. The other paths to it will see it (eventually). There are recent changes to multipath that have been checked in that don't try and write down all provider paths. There are other changes that need to go in as well to handle storage which is not, in fact, truly active-active. You have some kind of Santricity clone. The 94,1 error is saying "You don't own this path". From owner-freebsd-scsi@FreeBSD.ORG Tue Apr 13 17:57:10 2010 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 BBFA01065672 for ; Tue, 13 Apr 2010 17:57:10 +0000 (UTC) (envelope-from westr@connection.ca) Received: from nc-tor-mail2.connection.ca (nc-tor-mail2.connection.ca [205.207.122.27]) by mx1.freebsd.org (Postfix) with ESMTP id 9B3748FC13 for ; Tue, 13 Apr 2010 17:57:10 +0000 (UTC) Received: from westr-main.tor.connection.ca (external.tor.connection.ca [216.234.38.18]) by nc-tor-mail2.connection.ca (Postfix) with ESMTP id D04B174E5AD for ; Tue, 13 Apr 2010 13:57:09 -0400 (EDT) Date: Tue, 13 Apr 2010 13:57:10 -0400 From: Ross Organization: Network Connection X-Priority: 3 (Normal) Message-ID: <424621413.20100413135710@connection.ca> To: freebsd-scsi@freebsd.org In-Reply-To: <4BC35309.1010807@feral.com> References: <223938752.20100412130323@connection.ca> <4BC35309.1010807@feral.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re[2]: isp driver - sysctl controls missing X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ross List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Apr 2010 17:57:10 -0000 >> Anyone know if there's any reason for the sysctl is being pulled out, >> and the limits being so high? We use this in conjunction with geom >> multipath, so would prefer to fail over to another fc path asap when >> there's an issue. MJ> Sounds like a bug that I need to fix. Actually, it looks to be just a documentation "bug". Further reading of the source shows that in isp_pci.c, it now just reads the sysctl variables as driver hints (set in /boot/device.hints). That's probably the better way to do it since the values don't get changed once the system is booted. Good to see it's still modifiable! Cheers, Ross. -- From owner-freebsd-scsi@FreeBSD.ORG Tue Apr 13 18:01:26 2010 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 DEC4A1065675 for ; Tue, 13 Apr 2010 18:01:26 +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 A752A8FC17 for ; Tue, 13 Apr 2010 18:01:26 +0000 (UTC) Received: from [192.168.221.2] (remotevpn [192.168.221.2]) by ns1.feral.com (8.14.3/8.14.3) with ESMTP id o3DI1Prh041925 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 13 Apr 2010 11:01:26 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <4BC4B175.2040403@feral.com> Date: Tue, 13 Apr 2010 11:01:25 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc11 Thunderbird/3.0.4 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <223938752.20100412130323@connection.ca> <4BC35309.1010807@feral.com> <424621413.20100413135710@connection.ca> In-Reply-To: <424621413.20100413135710@connection.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.2.3 (ns1.feral.com [192.168.221.1]); Tue, 13 Apr 2010 11:01:26 -0700 (PDT) Subject: Re: isp driver - sysctl controls missing 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, 13 Apr 2010 18:01:27 -0000 On 04/13/2010 10:57 AM, Ross wrote: > >>> Anyone know if there's any reason for the sysctl is being pulled out, >>> and the limits being so high? We use this in conjunction with geom >>> multipath, so would prefer to fail over to another fc path asap when >>> there's an issue. >>> > MJ> Sounds like a bug that I need to fix. > > Actually, it looks to be just a documentation "bug". > > Further reading of the source shows that in isp_pci.c, it now just > reads the sysctl variables as driver hints (set in /boot/device.hints). > > That's probably the better way to do it since the values don't get > changed once the system is booted. > > Good to see it's still modifiable! > > Cheers, > Ross. > > It's something you might want to change. From owner-freebsd-scsi@FreeBSD.ORG Tue Apr 13 19:04:11 2010 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 D20BE1065670 for ; Tue, 13 Apr 2010 19:04:11 +0000 (UTC) (envelope-from westr@connection.ca) Received: from nc-tor-mail1.connection.ca (nc-tor-mail1.connection.ca [205.207.122.26]) by mx1.freebsd.org (Postfix) with ESMTP id AFD3D8FC1F for ; Tue, 13 Apr 2010 19:04:11 +0000 (UTC) Received: from westr-main.tor.connection.ca (external.tor.connection.ca [216.234.38.18]) by nc-tor-mail1.connection.ca (Postfix) with ESMTP id E90EA44B3C1 for ; Tue, 13 Apr 2010 15:04:10 -0400 (EDT) Date: Tue, 13 Apr 2010 15:04:11 -0400 From: Ross Organization: Network Connection X-Priority: 3 (Normal) Message-ID: <45852874.20100413150411@connection.ca> To: freebsd-scsi@freebsd.org In-Reply-To: <4BC4B175.2040403@feral.com> References: <223938752.20100412130323@connection.ca> <4BC35309.1010807@feral.com> <424621413.20100413135710@connection.ca> <4BC4B175.2040403@feral.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re[2]: isp driver - sysctl controls missing X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ross List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Apr 2010 19:04:11 -0000 >> Actually, it looks to be just a documentation "bug". >> MJ> It's something you might want to change. Oh man, documentation! I loooove that! :) But since you did the hard part in updating the code, I'll do up a PR with diff to update it shortly. Can you do a quick 5 second check over the man page to see if there's any glaring errors that I can fix at the same time when I do the new diff? http://www.freebsd.org/cgi/man.cgi?query=isp&sektion=0&manpath=FreeBSD+8.0-RELEASE&format=html Thanks, Ross. -- From owner-freebsd-scsi@FreeBSD.ORG Wed Apr 14 03:28:59 2010 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 B2BB01065670 for ; Wed, 14 Apr 2010 03:28:59 +0000 (UTC) (envelope-from erich@fuujingroup.com) Received: from fluorine.fuujinnetworks.com (fluorine.fuujinnetworks.com [64.90.67.234]) by mx1.freebsd.org (Postfix) with ESMTP id 8F8308FC18 for ; Wed, 14 Apr 2010 03:28:59 +0000 (UTC) Received: from [10.168.1.8] (copper.fuujinnetworks.com [64.90.67.254]) by fluorine.fuujinnetworks.com (Postfix) with ESMTPA id 53503439E38 for ; Tue, 13 Apr 2010 22:29:25 -0500 (CDT) Message-ID: <4BC54480.7030305@fuujingroup.com> Date: Tue, 13 Apr 2010 22:28:48 -0600 From: "Erich Jenkins, Fuujin Group Ltd" User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: MicroMemory 5425CN support and ZFS + NFS 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, 14 Apr 2010 03:28:59 -0000 Not sure if the NAND drivers being written at http://wiki.freebsd.org/NAND apply to this device or not. It appears this is more of a simulator at the moment and an experimental framework. Is there any current support for the MM-5425CN series NAND flash cards in FreeBSD? These seem like they'd be excellent for a separate ZIL in a ZFS raidz config if installed in pairs for mirroring... Here's the pciconf probe of the device in question: none3@pci0:6:2:0: class=0x058000 card=0x00000000 chip=0x54251332 rev=0x06 hdr=0x00 vendor = 'Micro Memory' device = 'MM-5425CN PCI 64/66 Memory Module with Battery Backup' class = memory Also, does anyone have any direct experience with ZFS + NFS? It seems like there's some disagreement on whether or not this taxes the host machine to the point that performance drops off significantly. -- Erich M. Jenkins Fuujin Group Limited "You should never, never doubt what no one is sure about." -- Gene Wilder