From owner-freebsd-stable@FreeBSD.ORG Thu Jun 30 21:40:19 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 23CC416A41C for ; Thu, 30 Jun 2005 21:40:19 +0000 (GMT) (envelope-from rand@meridian-enviro.com) Received: from newman.meridian-enviro.com (newman.meridian-enviro.com [207.109.235.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7B1443D1F for ; Thu, 30 Jun 2005 21:40:18 +0000 (GMT) (envelope-from rand@meridian-enviro.com) X-Envelope-To: freebsd-stable@freebsd.org Received: from delta.meridian-enviro.com (delta.meridian-enviro.com [10.10.10.43]) by newman.meridian-enviro.com (8.13.1/8.13.1) with ESMTP id j5ULeHdS021479; Thu, 30 Jun 2005 16:40:17 -0500 (CDT) (envelope-from rand@meridian-enviro.com) Received: (from rand@localhost) by delta.meridian-enviro.com (8.13.1/8.13.1/Submit) id j5ULe75R001104; Thu, 30 Jun 2005 16:40:07 -0500 (CDT) (envelope-from rand@delta.meridian-enviro.com) To: John-Mark Gurney References: <20050617213910.M90456@ganymede.hub.org> <200506180943.j5I9hcOF019234@hugo10.ka.punkt.de> <20050629212908.GG727@funkthat.com> From: rand@meridian-enviro.com (Douglas K. Rand) Date: 30 Jun 2005 16:40:07 -0500 In-Reply-To: <20050629212908.GG727@funkthat.com> Message-ID: <8764vva5hk.fsf@delta.meridian-enviro.com> Lines: 11 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: ClamAV 0.84/961/Thu Jun 30 10:34:15 2005 on newman.meridian-enviro.com X-Virus-Status: Clean 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 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 21:40:19 -0000 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.