From owner-freebsd-stable@FreeBSD.ORG Thu Jun 30 22:06:30 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03D2316A41C for ; Thu, 30 Jun 2005 22:06:30 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5395F43D48 for ; Thu, 30 Jun 2005 22:06:29 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id j5UM6S0Q099273; Thu, 30 Jun 2005 15:06:28 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id j5UM6RjQ099272; Thu, 30 Jun 2005 15:06:27 -0700 (PDT) (envelope-from jmg) Date: Thu, 30 Jun 2005 15:06:27 -0700 From: John-Mark Gurney To: "Douglas K. Rand" Message-ID: <20050630220626.GM727@funkthat.com> Mail-Followup-To: "Douglas K. Rand" , "Patrick M. Hausen" , freebsd-stable@freebsd.org References: <20050617213910.M90456@ganymede.hub.org> <200506180943.j5I9hcOF019234@hugo10.ka.punkt.de> <20050629212908.GG727@funkthat.com> <8764vva5hk.fsf@delta.meridian-enviro.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8764vva5hk.fsf@delta.meridian-enviro.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p1 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-stable@freebsd.org Subject: Re: What is considered "the best supported" RAID controller for 5.x? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2005 22:06:30 -0000 Douglas K. Rand wrote this message on Thu, Jun 30, 2005 at 16:40 -0500: > JM> Basicly a process will hang in either ffsfsn (fsync induces this > JM> write) or getblk (a read), and as far as I can find out, the io > JM> just never returns even though the underlying block device > JM> continues to work fine.. > > I know this is probably a stupid answer, but ... Have you upgraded > the firmware on the card? We have a number of ICP cards and with the > 2.39 firmware we can easily lockup the box with the behavior you > explain with a simple buildworld. Upgrading the firmware to 2.44 > solves the problem completely for us. Well, the problem is that it doesn't happen very often (only two systems it happened to once), i.e. not reproducable, and to make matters worse, we have 100+ systems in the field at client sites, so, w/o a definate YES this fixes it, we can't really go around upgrading firmware.. Plus, we have a lot of older cards, where the current firmware is 2.34 (though we are running on 2.32 for many of our cards)... so, we can't use the really new firmware... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."