From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 2 11:07:17 2012 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C6F910656D1 for ; Mon, 2 Apr 2012 11:07:17 +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 EA7008FC19 for ; Mon, 2 Apr 2012 11:07:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q32B7Ggw046909 for ; Mon, 2 Apr 2012 11:07:16 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q32B7Giq046907 for freebsd-scsi@FreeBSD.org; Mon, 2 Apr 2012 11:07:16 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 2 Apr 2012 11:07:16 GMT Message-Id: <201204021107.q32B7Giq046907@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, 02 Apr 2012 11:07:17 -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/165982 scsi [mpt] mpt instability, drive resets, and losses on Fre o kern/165740 scsi [cam] SCSI code must drain callbacks before free o kern/163713 scsi [aic7xxx] [patch] Add Adaptec29329LPE to aic79xx_pci.c o kern/162256 scsi [mpt] QUEUE FULL EVENT and 'mpt_cam_event: 0x0' o kern/161809 scsi [cam] [patch] set kern.cam.boot_delay via build option o kern/159412 scsi [ciss] 7.3 RELEASE: ciss0 ADAPTER HEARTBEAT FAILED err o kern/157770 scsi [iscsi] [panic] iscsi_initiator panic o kern/154432 scsi [xpt] run_interrupt_driven_hooks: still waiting after o kern/153514 scsi [cam] [panic] CAM related panic 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/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/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 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 50 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 2 21:00:13 2012 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 81B02106564A for ; Mon, 2 Apr 2012 21:00:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5344D8FC15 for ; Mon, 2 Apr 2012 21:00:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q32L0D5w097020 for ; Mon, 2 Apr 2012 21:00:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q32L0DWC097019; Mon, 2 Apr 2012 21:00:13 GMT (envelope-from gnats) Date: Mon, 2 Apr 2012 21:00:13 GMT Message-Id: <201204022100.q32L0DWC097019@freefall.freebsd.org> To: freebsd-scsi@FreeBSD.org From: Eric van Gyzen Cc: Subject: Re: kern/153514: [cam] [panic] CAM related panic X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Eric van Gyzen List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Apr 2012 21:00:13 -0000 The following reply was made to PR kern/153514; it has been noted by GNATS. From: Eric van Gyzen To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/153514: [cam] [panic] CAM related panic Date: Mon, 2 Apr 2012 15:56:03 -0500 Is it possible that r232358 fixed this PR? Eric From owner-freebsd-scsi@FreeBSD.ORG Tue Apr 3 12:45:09 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9F9D01065670; Tue, 3 Apr 2012 12:45:09 +0000 (UTC) (envelope-from matt.thyer@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 8FC618FC16; Tue, 3 Apr 2012 12:45:08 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so3547886wgb.31 for ; Tue, 03 Apr 2012 05:45:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FWv5MUYnTBigGYTk0+8f+fGyyxitJ55K9oCvqc3E9JM=; b=xHxgd+3hQNRuRTyYhqnqfW7Ub9y5WCD5x1ThE//b8vapsuqGFC/7WyGs0zAM08Ry60 EwJYrnESSU5FiQEWpIBUo9LlhQ0dGDp+sRIUQHjyFcCWFSeNt9L+mg+e4rKgO3WnucnP CIa3T4G/hYxo3RXnSjoPjRssefqV7YwB0g57fhM8HiJQCGpwAW+J3OE4mHHof1LrMKyo Hh9AuwgklF3OBCyg4Xz8tvrastCSUYK2JuoUcj3QRhcfLMfc7PYpZnFsOyXYfkRLUOrw +/wk5AzOuYUk1lHT1ZNvTp1EgWW+7QiDBm42AovNly7Wy040f2HWS5YPj4AXn7ifbypo vDRg== MIME-Version: 1.0 Received: by 10.180.88.164 with SMTP id bh4mr5914955wib.22.1333457107140; Tue, 03 Apr 2012 05:45:07 -0700 (PDT) Received: by 10.216.190.219 with HTTP; Tue, 3 Apr 2012 05:45:07 -0700 (PDT) In-Reply-To: <20120327172129.GA67307@nargothrond.kdm.org> References: <20120120204459.GA51162@nargothrond.kdm.org> <72898EA27A61484885D72A06BD9CECE8@multiplay.co.uk> <20120120232841.GA71874@nargothrond.kdm.org> <20120326132558.GB76647@in-addr.com> <20120327172129.GA67307@nargothrond.kdm.org> Date: Tue, 3 Apr 2012 22:15:07 +0930 Message-ID: From: Matt Thyer To: "Kenneth D. Merry" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "Desai, Kashyap" , Garrett Cooper , freebsd-current@freebsd.org, Steven Hartland , freebsd-scsi@freebsd.org Subject: Re: LSI supported mps(4) driver available 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, 03 Apr 2012 12:45:09 -0000 On 28 March 2012 03:51, Kenneth D. Merry wrote: > On Tue, Mar 27, 2012 at 23:50:31 +1030, Matt Thyer wrote: > > On 26 March 2012 23:55, Gary Palmer wrote: > > > > > On Mon, Mar 26, 2012 at 08:05:59PM +1030, Matt Thyer wrote: > > > > On Mar 26, 2012 3:43 AM, "Garrett Cooper" > wrote: > > > > > > > > > > On Sun, Mar 25, 2012 at 5:16 AM, Matt Thyer > > > wrote: > > > > > > Has this driver been MFC to 8-STABLE yet ? > > > > > > > > > > > > I'm asking because I updated my NAS on the 4th of March from > 8-STABLE > > > > > > r225723 to r232477 and am now seeing 157,000 interrupts per > second on > > > > irq > > > > > > 16 where my SuperMicro AOC-USAS2-L8i resides (this card uses the > LSI > > > > > > SAS2008 chip). > > > > > > > [snip] > > > > > > > > After encountering this problem I updated my firmware from phase 7 to > > > phase > > > > 11 but this did not fix things. > > > > > > > > My question is: "Is the LSI driver even in 8-STABLE yet?". > > > > > > > > If not I'll upgrade to 9-STABLE to get the new driver. > > > > > > > > If it is, then I want to downgrade to just before it came in to see > if > > > this > > > > high interrupt rate problem is fixed. > > > > > > I'm no export in svn, however: > > > > > > http://svnweb.freebsd.org/base?view=revision&revision=230922 > > > > > > would appear to suggest that the new driver is in 8-Stable > > > > > > Gary > > > > > > > It's painful to take this system back to r230921 due to intolerance for > > downtime from it's users so I'd like to investigate the cause of the > > problem and try patches/sysctls/whatever first. > > > > The drives I'm using are 7 x WDC WD20EARS-00M (3 are AB50, 4 are AB51) > and > > 1 x WD20EARX-00P AB51. > > The WD20EARX-00P AB51 is a SATA 3 (6 Gbps) drive but the others are all > > SATA 2 (3 Gbps). > > > > I know the driver doesn't like mixed speeds in IR mode but I'm flashed > with > > IT firmware as ZFS is doing my RAID (raidz2). > > > > I was having problems with the WD20EARX-00P AB51 drive being faulted by > ZFS > > until I updated the firmware to 11 and now ZFS is happy (I've also done a > > full extended drive SMART test and the drive is fine). > > > > So what do people suggest (before reversion to r230921) ? > > If you're going to prove that it's the new LSI driver, you will probably > have to go back to the old driver. > > You don't have to back out your entire tree, you can just back out the > driver itself if you have an SVN tree. You can go into sys/dev/mps and do: > > svn update -r 230714 > > And then edit sys/conf/files and comment out these three lines: > > dev/mps/mps_config.c optional mps > dev/mps/mps_mapping.c optional mps > dev/mps/mps_sas_lsi.c optional mps > > Then you should be able to rebuild your kernel with the old driver and see > if the problem occurs again. > > Ken > -- > Kenneth Merry > ken@FreeBSD.ORG > This didn't work for me so I removed my /usr/src and checked out 8-STABLE at revision 230921 (svn checkout -r 230921 http://svn.freebsd.org/base/stable/8 /usr/src). I've built world, kernel etc and installed it using GENERIC kernel done my mergemaster, delete old, delete old-libs and I still have the problem. I'm wondering if it's due to the single 6 Gb drive in my raidz2 (the other 7 are 3 Gb). I've heard that the new driver doesn't like mixed speeds in a raid set when using -IR firmware but I wouldn't expect an issue with ZFS with -IT firmware. It seems that there may be a general incompatibility with both the old and new drivers and the Western Digital WD20EARX-00P 6 Gbps drive. Unfortunately I cannot get the old 3 Gb drive anymore. I'll try moving the WD20EARX-00P drive to the on board SATA ports next. From owner-freebsd-scsi@FreeBSD.ORG Tue Apr 3 13:22:29 2012 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 0E36B106564A; Tue, 3 Apr 2012 13:22:29 +0000 (UTC) (envelope-from matt.thyer@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 0AE698FC16; Tue, 3 Apr 2012 13:22:27 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so3583478wgb.31 for ; Tue, 03 Apr 2012 06:22:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/J6ZLiik3d1kDg8jWZRn+NGvPAhNZrHaEJFWbAxVWvs=; b=l4mOwnsxBd6X4cOUC9bufpmWTxIbRvjJgCKbQITH/a7HuoFEdqQ5Zb+CMBNIr7/bAL ufS4x3yB/FZb0tMoXd2wkx1dar5r7jfubD73jlXeVmJKiXfCjXKS6oHQHhJgI2inxjme dsxemxUNoDc0qC7z0eW/tQGw5s2AWssWqkmpZ/3SFaxKkSWR5XIfvA7uIGLkblo4jvL3 5kZV0jvJ4Oz3Nz7t+zrnrMwU8UlfIsOOyS45iEmfOzotdbzmNvRUggoIASQehdu52kOn W5SywWU84mmyE0WFFbRdOqUcOt3HuxFfx6wM8OJ9Fav5KnXjOApgsC3HioYO8h4vg3Sy I/hw== MIME-Version: 1.0 Received: by 10.180.105.194 with SMTP id go2mr34437424wib.22.1333459347176; Tue, 03 Apr 2012 06:22:27 -0700 (PDT) Received: by 10.216.190.219 with HTTP; Tue, 3 Apr 2012 06:22:25 -0700 (PDT) Received: by 10.216.190.219 with HTTP; Tue, 3 Apr 2012 06:22:25 -0700 (PDT) In-Reply-To: References: <20120120204459.GA51162@nargothrond.kdm.org> <72898EA27A61484885D72A06BD9CECE8@multiplay.co.uk> <20120120232841.GA71874@nargothrond.kdm.org> <20120326132558.GB76647@in-addr.com> Date: Tue, 3 Apr 2012 22:52:25 +0930 Message-ID: From: Matt Thyer To: Gary Palmer Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Garrett Cooper , freebsd-scsi@freebsd.org, freebsd-current@freebsd.org, "Kenneth D. Merry" , Steven Hartland Subject: Re: LSI supported mps(4) driver available 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, 03 Apr 2012 13:22:29 -0000 On Mar 27, 2012 11:50 PM, "Matt Thyer" wrote: > > I was having problems with the WD20EARX-00P AB51 drive being faulted by ZFS until I updated the firmware to 11 and now ZFS is happy (I've also done a full extended drive SMART test and the drive is fine). > I forgot to mention that I'm still having problems after this phase 11 firmware upgrade with the 6 Gbps drive being kicked out of the raidz2 with write errors (even though a SMART full surface test says the drive is OK). This leads me to think that both the old and new drivers have a problem with the 6 Gbps WD20EARX-00P AB51 drive. Now that the 6 Gbps drive is on the Intel SATA controller things seem OK but it's a bit early to tell. Stay tuned! From owner-freebsd-scsi@FreeBSD.ORG Tue Apr 3 13:42:48 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 824171065673; Tue, 3 Apr 2012 13:42:48 +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 441B38FC18; Tue, 3 Apr 2012 13:42:48 +0000 (UTC) Received: from gjp by noop.in-addr.com with local (Exim 4.77 (FreeBSD)) (envelope-from ) id 1SF405-000P2a-P6; Tue, 03 Apr 2012 09:42:21 -0400 Date: Tue, 3 Apr 2012 09:42:21 -0400 From: Gary Palmer To: Matt Thyer Message-ID: <20120403134221.GA87802@in-addr.com> References: <20120120204459.GA51162@nargothrond.kdm.org> <72898EA27A61484885D72A06BD9CECE8@multiplay.co.uk> <20120120232841.GA71874@nargothrond.kdm.org> <20120326132558.GB76647@in-addr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on noop.in-addr.com); SAEximRunCond expanded to false Cc: Garrett Cooper , freebsd-scsi@freebsd.org, freebsd-current@freebsd.org, "Kenneth D. Merry" , Steven Hartland Subject: Re: LSI supported mps(4) driver available 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, 03 Apr 2012 13:42:48 -0000 On Tue, Apr 03, 2012 at 10:52:25PM +0930, Matt Thyer wrote: > On Mar 27, 2012 11:50 PM, "Matt Thyer" wrote: > > > > I was having problems with the WD20EARX-00P AB51 drive being faulted by > ZFS until I updated the firmware to 11 and now ZFS is happy (I've also done > a full extended drive SMART test and the drive is fine). > > > I forgot to mention that I'm still having problems after this phase 11 > firmware upgrade with the 6 Gbps drive being kicked out of the raidz2 with > write errors (even though a SMART full surface test says the drive is OK). > > This leads me to think that both the old and new drivers have a problem > with the 6 Gbps WD20EARX-00P AB51 drive. > > Now that the 6 Gbps drive is on the Intel SATA controller things seem OK > but it's a bit early to tell. > > Stay tuned! I think you should contact either SuperMicro or LSI and open a support case as it looks like there could be a problem with either the controller or the firmware when presented with mixed speed devices. Either way I think this needs to be escalated to the manufacturer. Regards, Gary From owner-freebsd-scsi@FreeBSD.ORG Wed Apr 4 05:33:12 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DBDDF106564A; Wed, 4 Apr 2012 05:33:12 +0000 (UTC) (envelope-from Kashyap.Desai@lsi.com) Received: from psmtp.com (na3sys009aog137.obsmtp.com [74.125.149.18]) by mx1.freebsd.org (Postfix) with ESMTP id 2FA5E8FC14; Wed, 4 Apr 2012 05:33:12 +0000 (UTC) Received: from paledge01.lsi.com ([192.19.193.42]) (using TLSv1) by na3sys009aob137.postini.com ([74.125.148.12]) with SMTP ID DSNKT3vdF+Ua4bZsSL5XFamawUPR5nD3WTEM@postini.com; Tue, 03 Apr 2012 22:33:12 PDT Received: from PALCAS01.lsi.com (128.94.213.117) by PALEDGE01.lsi.com (192.19.193.42) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 4 Apr 2012 01:38:28 -0400 Received: from inbexch02.lsi.com (135.36.98.40) by PALCAS01.lsi.com (128.94.213.117) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 4 Apr 2012 01:33:10 -0400 Received: from inbmail01.lsi.com ([135.36.98.64]) by inbexch02.lsi.com ([135.36.98.40]) with mapi; Wed, 4 Apr 2012 11:03:07 +0530 From: "Desai, Kashyap" To: "freebsd-scsi@freebsd.org" Date: Wed, 4 Apr 2012 11:03:04 +0530 Thread-Topic: FreeBSD multi Lun detection query Thread-Index: Ac0SJGie/YKg6b12RkOKg4ltCy7eOQ== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "gibbs@freebsd.org" , "ken@freebsd.org" , "McConnell, Stephen" Subject: FreeBSD multi Lun detection query 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, 04 Apr 2012 05:33:12 -0000 Hi, Our test team has one test case, where they need to verify multi lun detect= ion by FreeBS8.2 OS. Here are the steps to reproduce. Step 1: Configured Multi-Luns in RBOD (DOTHILL) and map to controller which= is booted with FreeBSD Step 2: Issue the command "camcontrol rescan all" and "camcontrol dev" Expected Result: the command should display all the configured luns Actual Result: Only the first Lun is discovered Note: When we issue explicit scan using "camcontrol rescan bus:target:lun",= it detects that specific lun. Query: How does FreeBSD detect multi luns ? Driver issue XPT_BUS_RESCAN and= expect OS should detect both the luns. Is there any limitation associated with multi lun in FreeBSD ? Thanks, Kashyap From owner-freebsd-scsi@FreeBSD.ORG Wed Apr 4 12:32:07 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 664A2106564A; Wed, 4 Apr 2012 12:32:07 +0000 (UTC) (envelope-from matt.thyer@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 347A58FC12; Wed, 4 Apr 2012 12:32:06 +0000 (UTC) Received: by lagv3 with SMTP id v3so440763lag.13 for ; Wed, 04 Apr 2012 05:32:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tOeYRhGGdCz0yZT3MtSehKdV5z36bpQ/F0Yh7+z/eMw=; b=YOFuX1zeURnV4noZ5EXLW6Zgto5ergBZ6BqfghBbRIPTTtzHap+i+/861IOogqsuej 0v0fXgBOkDM6DUhboD520163SXHIYLtPKFpdt39IsJz4I9PQPc/FBl1owbwRMEuILBiK BimZtSr7nM45CD+bjBsdSiN6G+g6pJ4AIqUv1M8lB/+taZ3QQJEiURvU/1tGrv+BmXrz vNw42D3YM4c9bvkS5rvei78iIcNnBjp1YJk/KUzPFMw79iP11W2gQEzDfiRiSh/PWx6B VuhNadSmFLRXpwspLhTpYC/7IpcQni2dVS4phioxm+ioFLorYpc2iV7RevtaRY6SlHsu 3h0A== MIME-Version: 1.0 Received: by 10.152.110.116 with SMTP id hz20mr18469170lab.33.1333542725103; Wed, 04 Apr 2012 05:32:05 -0700 (PDT) Received: by 10.112.80.33 with HTTP; Wed, 4 Apr 2012 05:32:04 -0700 (PDT) In-Reply-To: <20120403134221.GA87802@in-addr.com> References: <20120120204459.GA51162@nargothrond.kdm.org> <72898EA27A61484885D72A06BD9CECE8@multiplay.co.uk> <20120120232841.GA71874@nargothrond.kdm.org> <20120326132558.GB76647@in-addr.com> <20120403134221.GA87802@in-addr.com> Date: Wed, 4 Apr 2012 22:02:04 +0930 Message-ID: From: Matt Thyer To: Gary Palmer Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Garrett Cooper , freebsd-scsi@freebsd.org, freebsd-current@freebsd.org, "Kenneth D. Merry" , Steven Hartland Subject: Re: LSI supported mps(4) driver available 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, 04 Apr 2012 12:32:07 -0000 On 3 April 2012 23:12, Gary Palmer wrote: > On Tue, Apr 03, 2012 at 10:52:25PM +0930, Matt Thyer wrote: > > I forgot to mention that I'm still having problems after this phase 11 > > firmware upgrade with the 6 Gbps drive being kicked out of the raidz2 > with > > write errors (even though a SMART full surface test says the drive is > OK). > > > > This leads me to think that both the old and new drivers have a problem > > with the 6 Gbps WD20EARX-00P AB51 drive. > > > > Now that the 6 Gbps drive is on the Intel SATA controller things seem OK > > but it's a bit early to tell. > > > > Stay tuned! > > I think you should contact either SuperMicro or LSI and open a support > case as it looks like there could be a problem with either the controller > or the firmware when presented with mixed speed devices. Either way I > think > this needs to be escalated to the manufacturer. > > Regards, > > Gary > I'm now having no problems since moving the SATA 3 drive to the on board Intel controller. I'll try to report this to Super Micro & LSI. From owner-freebsd-scsi@FreeBSD.ORG Wed Apr 4 15:28:02 2012 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 A6E261065672; Wed, 4 Apr 2012 15:28:02 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id 6E0418FC18; Wed, 4 Apr 2012 15:28:02 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id q34FS1nk070796; Wed, 4 Apr 2012 09:28:01 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id q34FS1HE070795; Wed, 4 Apr 2012 09:28:01 -0600 (MDT) (envelope-from ken) Date: Wed, 4 Apr 2012 09:28:01 -0600 From: "Kenneth D. Merry" To: "Desai, Kashyap" Message-ID: <20120404152801.GA70760@nargothrond.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Cc: "freebsd-scsi@freebsd.org" , "gibbs@freebsd.org" , "McConnell, Stephen" Subject: Re: FreeBSD multi Lun detection query 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, 04 Apr 2012 15:28:02 -0000 On Wed, Apr 04, 2012 at 11:03:04 +0530, Desai, Kashyap wrote: > Hi, > > Our test team has one test case, where they need to verify multi lun detection by FreeBS8.2 OS. > Here are the steps to reproduce. > > Step 1: Configured Multi-Luns in RBOD (DOTHILL) and map to controller which is booted with FreeBSD > Step 2: Issue the command "camcontrol rescan all" and "camcontrol dev" > > Expected Result: the command should display all the configured luns > > Actual Result: Only the first Lun is discovered > > Note: When we issue explicit scan using "camcontrol rescan bus:target:lun", it detects that specific lun. > > Query: How does FreeBSD detect multi luns ? Driver issue XPT_BUS_RESCAN and expect OS should detect both the luns. > Is there any limitation associated with multi lun in FreeBSD ? A couple of questions: - Do you have change 231716 in your version of the driver? The max_lun field of the path inquiry CCB was set to 0, which disabled multiple LUN scanning. I set it to 8, but in reality it needs to be set to the maximum LUN supported by the chip. - What LUN numbers do you have configured on the array? Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Wed Apr 4 17:41:35 2012 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 4371A1065672; Wed, 4 Apr 2012 17:41:35 +0000 (UTC) (envelope-from Kashyap.Desai@lsi.com) Received: from psmtp.com (na3sys009aog135.obsmtp.com [74.125.149.84]) by mx1.freebsd.org (Postfix) with ESMTP id 85C658FC14; Wed, 4 Apr 2012 17:41:34 +0000 (UTC) Received: from paledge01.lsi.com ([192.19.193.42]) (using TLSv1) by na3sys009aob135.postini.com ([74.125.148.12]) with SMTP ID DSNKT3yHyLeArp5wBt/dXJEuN5Utq2PCDrFL@postini.com; Wed, 04 Apr 2012 10:41:34 PDT Received: from PALCAS01.lsi.com (128.94.213.117) by PALEDGE01.lsi.com (192.19.193.42) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 4 Apr 2012 13:46:43 -0400 Received: from inbexch02.lsi.com (135.36.98.40) by PALCAS01.lsi.com (128.94.213.117) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 4 Apr 2012 13:41:27 -0400 Received: from inbmail01.lsi.com ([135.36.98.64]) by inbexch02.lsi.com ([135.36.98.40]) with mapi; Wed, 4 Apr 2012 23:11:23 +0530 From: "Desai, Kashyap" To: "Kenneth D. Merry" Date: Wed, 4 Apr 2012 23:11:22 +0530 Thread-Topic: FreeBSD multi Lun detection query Thread-Index: Ac0Sd4nlo1bl9ZPKTQ2n3vfK/rJvqAAEjXpg Message-ID: References: <20120404152801.GA70760@nargothrond.kdm.org> In-Reply-To: <20120404152801.GA70760@nargothrond.kdm.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-scsi@freebsd.org" , "gibbs@freebsd.org" , "McConnell, Stephen" Subject: RE: FreeBSD multi Lun detection query 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, 04 Apr 2012 17:41:35 -0000 > -----Original Message----- > From: Kenneth D. Merry [mailto:ken@freebsd.org] > Sent: Wednesday, April 04, 2012 8:58 PM > To: Desai, Kashyap > Cc: freebsd-scsi@freebsd.org; McConnell, Stephen; gibbs@freebsd.org > Subject: Re: FreeBSD multi Lun detection query >=20 > On Wed, Apr 04, 2012 at 11:03:04 +0530, Desai, Kashyap wrote: > > Hi, > > > > Our test team has one test case, where they need to verify multi lun > detection by FreeBS8.2 OS. > > Here are the steps to reproduce. > > > > Step 1: Configured Multi-Luns in RBOD (DOTHILL) and map to controller > which is booted with FreeBSD > > Step 2: Issue the command "camcontrol rescan all" and "camcontrol dev" > > > > Expected Result: the command should display all the configured luns > > > > Actual Result: Only the first Lun is discovered > > > > Note: When we issue explicit scan using "camcontrol rescan > bus:target:lun", it detects that specific lun. > > > > Query: How does FreeBSD detect multi luns ? Driver issue > XPT_BUS_RESCAN and expect OS should detect both the luns. > > Is there any limitation associated with multi lun in FreeBSD ? >=20 > A couple of questions: >=20 > - Do you have change 231716 in your version of the driver? The max_lun > field of the path inquiry CCB was set to 0, which disabled multiple > LUN > scanning. I set it to 8, but in reality it needs to be set to the > maximum LUN supported by the chip. Hi Ken, This is very good information. I was not aware of this max_lun fiel= d. We used FreeBSD-8.2-RELEASE. I can ask test team to verify with latest upst= ream.(rev 231716) What about FreeBSD-9-RELEASE ? Is max_luns are set to non-zero. ? >=20 > - What LUN numbers do you have configured on the array? Not sure what is correct answer for this. _but_ we have created two luns. A= nd expected to see lun 0 and lun 1. ~ Kashyap >=20 > Ken > -- > Kenneth Merry > ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Thu Apr 5 14:57:43 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 41DFA106564A for ; Thu, 5 Apr 2012 14:57:43 +0000 (UTC) (envelope-from buddy@telenet.ru) Received: from k66.ru (mail.telenet.ru [87.224.128.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9E8D78FC14 for ; Thu, 5 Apr 2012 14:57:41 +0000 (UTC) Received: from [87.224.188.131] (account buddy@telenet.ru HELO minimachine.hq.telenet.ru) by k66.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPSA id 26125199; Thu, 05 Apr 2012 20:57:40 +0600 Date: Thu, 5 Apr 2012 20:57:41 +0600 From: Andrew Alcheyev Organization: Telenet-Service Ltd. X-Priority: 3 (Normal) Message-ID: <596341805.20120405205741@telenet.ru> To: freebsd-scsi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 8bit Cc: Marius Strobl Subject: mpt(4): some trouble with mixing LSI SAS1078 and LSI FC 7104EP X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andrew Alcheyev List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Apr 2012 14:57:43 -0000 Hello, freebsd-scsi. Today I ran into some strange problem while launching two mpt(4) cards simultaneously within the same host. Each one in itself works fine but together they cause the kernel to panic when probing devices. It seems the trouble is that both cards are steered by the same device driver, mpt(4), and the trouble arises when disks should be attached to the corresponding device. The first device (mpt0) is Fibre Channel PCIe card LSI 7104EP - which worked great for several years along with another RAID (amr(4), if it matters) within another host. The second one (mpt1) is LSI SAS 1078 - RAID controller integrated into Intel's platform SR2600URLXR (I had to get fresh 9-stable kernel to bring this card up). The other part of problem that I could not get any sensitive information from the kernel because it hangs as soon as it discovers some disks at the RAID controller (the existence of any disks at FC-card makes no difference). The USB keyboard hangs (or whatever in the kernel) as well at the same moment so I can't do any magic through in-kernel debugger nor get any dump. So far I stuck with 2 questions: - did anybody have any luck with mupltiple mpt(4) cards within a single host? - what can I do to resolve this trouble? With the best regards, Andrew. From owner-freebsd-scsi@FreeBSD.ORG Thu Apr 5 20:01:30 2012 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 C0844106566C; Thu, 5 Apr 2012 20:01:30 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id 690028FC08; Thu, 5 Apr 2012 20:01:30 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id q35K1OOY065141; Thu, 5 Apr 2012 14:01:24 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id q35K1ONp065140; Thu, 5 Apr 2012 14:01:24 -0600 (MDT) (envelope-from ken) Date: Thu, 5 Apr 2012 14:01:24 -0600 From: "Kenneth D. Merry" To: "Desai, Kashyap" Message-ID: <20120405200124.GA64019@nargothrond.kdm.org> References: <20120404152801.GA70760@nargothrond.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Cc: "freebsd-scsi@freebsd.org" , "gibbs@freebsd.org" , "McConnell, Stephen" Subject: Re: FreeBSD multi Lun detection query 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, 05 Apr 2012 20:01:30 -0000 On Wed, Apr 04, 2012 at 23:11:22 +0530, Desai, Kashyap wrote: > > > > -----Original Message----- > > From: Kenneth D. Merry [mailto:ken@freebsd.org] > > Sent: Wednesday, April 04, 2012 8:58 PM > > To: Desai, Kashyap > > Cc: freebsd-scsi@freebsd.org; McConnell, Stephen; gibbs@freebsd.org > > Subject: Re: FreeBSD multi Lun detection query > > > > On Wed, Apr 04, 2012 at 11:03:04 +0530, Desai, Kashyap wrote: > > > Hi, > > > > > > Our test team has one test case, where they need to verify multi lun > > detection by FreeBS8.2 OS. > > > Here are the steps to reproduce. > > > > > > Step 1: Configured Multi-Luns in RBOD (DOTHILL) and map to controller > > which is booted with FreeBSD > > > Step 2: Issue the command "camcontrol rescan all" and "camcontrol dev" > > > > > > Expected Result: the command should display all the configured luns > > > > > > Actual Result: Only the first Lun is discovered > > > > > > Note: When we issue explicit scan using "camcontrol rescan > > bus:target:lun", it detects that specific lun. > > > > > > Query: How does FreeBSD detect multi luns ? Driver issue > > XPT_BUS_RESCAN and expect OS should detect both the luns. > > > Is there any limitation associated with multi lun in FreeBSD ? > > > > A couple of questions: > > > > - Do you have change 231716 in your version of the driver? The max_lun > > field of the path inquiry CCB was set to 0, which disabled multiple > > LUN > > scanning. I set it to 8, but in reality it needs to be set to the > > maximum LUN supported by the chip. > > Hi Ken, This is very good information. I was not aware of this max_lun field. > We used FreeBSD-8.2-RELEASE. I can ask test team to verify with latest upstream.(rev 231716) > If you were using 8.2, were you using your own mpslsi driver with it? I'm guessing that your version of the mps driver didn't have the max_lun change. > What about FreeBSD-9-RELEASE ? Is max_luns are set to non-zero. ? The max_lun field needs to be set by the driver. The version of the old mps driver in 9.0 release did set the max_lun field to a non-zero value. But if you were using the mpslsi driver, it probably didn't have that change. > > - What LUN numbers do you have configured on the array? > > Not sure what is correct answer for this. _but_ we have created two luns. And expected to see lun 0 and lun 1. > There is no correct or incorrect answer, but both LUNs should be probed if the max_lun field in the path inquiry CCB returned by the driver is non-zero. What is the maximum LUN number supported by the hardware? You should set the max_lun field to whatever that number is. Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Fri Apr 6 09:27:34 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 517AB106564A; Fri, 6 Apr 2012 09:27:34 +0000 (UTC) (envelope-from buddy@telenet.ru) Received: from k66.ru (mail.telenet.ru [87.224.128.3]) by mx1.freebsd.org (Postfix) with ESMTP id 6C76F8FC08; Fri, 6 Apr 2012 09:27:33 +0000 (UTC) Received: from [87.224.188.131] (account buddy@telenet.ru HELO minimachine.hq.telenet.ru) by k66.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPSA id 26365549; Fri, 06 Apr 2012 15:27:31 +0600 Date: Fri, 6 Apr 2012 15:27:31 +0600 From: Andrew Alcheyev Organization: Telenet-Service Ltd. X-Priority: 3 (Normal) Message-ID: <248169346.20120406152731@telenet.ru> To: freebsd-scsi@freebsd.org In-Reply-To: <1206318535.3120843.1333639067905.JavaMail.root@merit-mailstore01> References: <596341805.20120405205741@telenet.ru> <1206318535.3120843.1333639067905.JavaMail.root@merit-mailstore01> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: "Kenneth D. Merry" , Marius Strobl Subject: Re[2]: mpt(4): some trouble with mixing LSI SAS1078 and LSI FC 7104EP X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andrew Alcheyev List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Apr 2012 09:27:34 -0000 Hello, freebsd-scsi. It seems I solved my problem. It happened that the bug I collided with had been already discussed in http://www.freebsd.org/cgi/getmsg.cgi?fetch=92840+0+/usr/local/www/db/text/2012/freebsd-scsi/20120311.freebsd-scsi So I applied the patch attached and since then everything is going well. Thank you, Kenneth and Marius, for great work! With the best regards, Andrew. P.S. I'm still a bit curious why did my devices work pretty nice separately. On Thursday, April 5, 2012, 9:17:47 PM you were writing: KC> you did check that none of the disks are bad? I have had some odd KC> things happen to me with newer LSI cards on mpt(4) when drives go KC> bad. please disregard this question if this is what you mean by each one in itself works fine. KC> ----- Original Message ----- KC> From: "Andrew Alcheyev" KC> To: freebsd-scsi@freebsd.org KC> Cc: "Marius Strobl" KC> Sent: Thursday, April 5, 2012 10:57:41 AM KC> Subject: mpt(4): some trouble with mixing LSI SAS1078 and LSI FC 7104EP KC> Hello, freebsd-scsi. KC> Today I ran into some strange problem while launching two mpt(4) cards KC> simultaneously within the same host. Each one in itself works fine but KC> together they cause the kernel to panic when probing devices. KC> It seems the trouble is that both cards are steered by the same device KC> driver, mpt(4), and the trouble arises when disks should be attached KC> to the corresponding device. KC> The first device (mpt0) is Fibre Channel PCIe card LSI 7104EP - which KC> worked great for several years along with another RAID (amr(4), if it KC> matters) within another host. KC> The second one (mpt1) is LSI SAS 1078 - RAID controller integrated into KC> Intel's platform SR2600URLXR (I had to get fresh 9-stable kernel to KC> bring this card up). KC> The other part of problem that I could not get any sensitive KC> information from the kernel because it hangs as soon as it discovers KC> some disks at the RAID controller (the existence of any disks at KC> FC-card makes no difference). The USB keyboard hangs (or whatever in KC> the kernel) as well at the same moment so I can't do any magic through KC> in-kernel debugger nor get any dump. KC> So far I stuck with 2 questions: KC> - did anybody have any luck with mupltiple mpt(4) cards within a KC> single host? KC> - what can I do to resolve this trouble? KC> With the best regards, Andrew. KC> _______________________________________________ KC> freebsd-scsi@freebsd.org mailing list KC> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi KC> To unsubscribe, send any mail to KC> "freebsd-scsi-unsubscribe@freebsd.org" From owner-freebsd-scsi@FreeBSD.ORG Fri Apr 6 10:01:47 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E17EC106564A; Fri, 6 Apr 2012 10:01:47 +0000 (UTC) (envelope-from Kashyap.Desai@lsi.com) Received: from na3sys009aog113.obsmtp.com (na3sys009aog113.obsmtp.com [74.125.149.209]) by mx1.freebsd.org (Postfix) with ESMTP id C6AD08FC1C; Fri, 6 Apr 2012 10:01:46 +0000 (UTC) Received: from paledge01.lsi.com ([192.19.193.42]) (using TLSv1) by na3sys009aob113.postini.com ([74.125.148.12]) with SMTP ID DSNKT36/CRKAmz+3PM+PosHmsjEzR9zVa8lL@postini.com; Fri, 06 Apr 2012 03:01:47 PDT Received: from PALHUB01.lsi.com (128.94.213.114) by PALEDGE01.lsi.com (192.19.193.42) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 6 Apr 2012 06:06:57 -0400 Received: from inbexch02.lsi.com (135.36.98.40) by PALHUB01.lsi.com (128.94.213.114) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 6 Apr 2012 06:01:43 -0400 Received: from inbmail01.lsi.com ([135.36.98.64]) by inbexch02.lsi.com ([135.36.98.40]) with mapi; Fri, 6 Apr 2012 15:31:41 +0530 From: "Desai, Kashyap" To: "freebsd-scsi@freebsd.org" , "freebsd-fs@freebsd.org" Date: Fri, 6 Apr 2012 15:31:39 +0530 Thread-Topic: Kernel crash at "softdep_deallocate_dependencies" Thread-Index: Ac0T3EKQWAnorhNWQtCpeQSByo4SAg== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "gibbs@freebsd.org" , "Kenneth D.Merry" , "McConnell, Stephen" Subject: Kernel crash at "softdep_deallocate_dependencies" 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, 06 Apr 2012 10:01:48 -0000 Hi, Thanks in advance for looking this query and hoping for some help from = File system experts. We have a RAID 0 volume which has partition (created using sysinstall fdisk= option). While IOs are in progress removing one of the volume member kernel panic is= hit with the following messages g_vfs_done():(da0:da0s1d[WRITE(offset=3D6358872064, length=3D2048)]mpslsi0:= 0:error =3D 6 0:/home: got error 6 while accessing filesystem 0): panic: softdep_deallocate_dependencies: unrecovered I/O error lost device Note: 1. The issue is also seen on a RAID 0 volume which does not have a partitio= n on it. 2. Issue was observed on both SAS and SATA drives. 3. When we send IOs to the driver without FS (using "dd" command), kernel p= anic never seen. I have searched on this topic and looks like something wrong with FS. _but_= I don't have any trigger to support that this is not Driver issue. When we tried below options: (disable Journal on FS) Things does not change= . We still see kernel panic. umount tunefs -j disable mount cd rm .sujournal Any thoughts ? ` Kashyap From owner-freebsd-scsi@FreeBSD.ORG Fri Apr 6 13:01:45 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B3A0D106566B; Fri, 6 Apr 2012 13:01:45 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id 5D33A8FC0A; Fri, 6 Apr 2012 13:01:45 +0000 (UTC) Received: from localhost (58.wheelsystems.com [83.12.187.58]) by mail.dawidek.net (Postfix) with ESMTPSA id E5045CA1; Fri, 6 Apr 2012 15:01:37 +0200 (CEST) Date: Fri, 6 Apr 2012 15:00:06 +0200 From: Pawel Jakub Dawidek To: "Desai, Kashyap" Message-ID: <20120406130006.GC1336@garage.freebsd.pl> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KN5l+BnMqAQyZLvT" Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-fs@freebsd.org" , "freebsd-scsi@freebsd.org" , "Kenneth D.Merry" , "McConnell, Stephen" Subject: Re: Kernel crash at "softdep_deallocate_dependencies" 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, 06 Apr 2012 13:01:45 -0000 --KN5l+BnMqAQyZLvT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 06, 2012 at 03:31:39PM +0530, Desai, Kashyap wrote: > Hi, Thanks in advance for looking this query and hoping for some help fro= m File system experts. >=20 > We have a RAID 0 volume which has partition (created using sysinstall fdi= sk option). > While IOs are in progress removing one of the volume member kernel panic = is hit with the following messages >=20 > g_vfs_done():(da0:da0s1d[WRITE(offset=3D6358872064, length=3D2048)]mpslsi= 0:0:error =3D 6 > 0:/home: got error 6 while accessing filesystem > 0): panic: softdep_deallocate_dependencies: unrecovered I/O error > lost device >=20 > Note: > 1. The issue is also seen on a RAID 0 volume which does not have a partit= ion on it. > 2. Issue was observed on both SAS and SATA drives. > 3. When we send IOs to the driver without FS (using "dd" command), kernel= panic never seen. >=20 >=20 > I have searched on this topic and looks like something wrong with FS. _bu= t_ I don't have any trigger to support that this is not Driver issue. This might be lame error handling on the FS side, but FS is not here to blame. You get I/O error from device below. In case of RAID0 you have no redundancy, so you cannot expect anything good by removing one of its components. Using "dd" doesn't trigger kernel panic, because I/O error is handled by userland process (it exits). > When we tried below options: (disable Journal on FS) Things does not chan= ge. We still see kernel panic. >=20 > umount > tunefs -j disable > mount > cd > rm .sujournal >=20 > Any thoughts ? What behaviour would you expect when your RAID0 volume dies? The best thing to do here would be to either stop all I/Os until the component is back or forcibly unmount the file system, but both options are probably hard to get right. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl --KN5l+BnMqAQyZLvT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk9+6NYACgkQForvXbEpPzTujQCg3rzzLyyVrVc/UtdrmFbb9PHA nxsAoOo1fZRtJoYUw+lIM2nKWqT9Xm0p =E9dp -----END PGP SIGNATURE----- --KN5l+BnMqAQyZLvT--