From owner-freebsd-stable@FreeBSD.ORG Fri Jan 6 00:09:35 2006 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 D94AE16A41F for ; Fri, 6 Jan 2006 00:09:35 +0000 (GMT) (envelope-from dsze@mail.distrust.net) Received: from mail.distrust.net (mail.distrust.net [69.93.230.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 536F843D5C for ; Fri, 6 Jan 2006 00:09:35 +0000 (GMT) (envelope-from dsze@mail.distrust.net) Received: from mail.distrust.net (localhost [127.0.0.1]) by mail.distrust.net (8.13.3/8.13.3) with ESMTP id k06099jS001314; Thu, 5 Jan 2006 18:09:09 -0600 (CST) (envelope-from dsze@mail.distrust.net) Received: (from dsze@localhost) by mail.distrust.net (8.13.3/8.13.3/Submit) id k06099MK001313; Thu, 5 Jan 2006 18:09:09 -0600 (CST) (envelope-from dsze) Date: Thu, 5 Jan 2006 18:09:09 -0600 From: David Sze To: Doug White Message-ID: <20060106000909.GA97739@mail.distrust.net> References: <20060105224150.GA991@tuatara.fishballoon.org> <20060105153250.D58957@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060105153250.D58957@carver.gumbysoft.com> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV 0.87.1/1230/Thu Jan 5 05:49:56 2006 on mail.distrust.net X-Virus-Status: Clean Cc: Scott Mitchell , freebsd-stable@freebsd.org Subject: Re: 6.0 on Dell 1850 with PERC4e/DC RAID? 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: Fri, 06 Jan 2006 00:09:36 -0000 On Thu, Jan 05, 2006 at 03:34:24PM -0800, Doug White wrote: > On Thu, 5 Jan 2006, Scott Mitchell wrote: > > > Hi all, > > > > I may be getting a new Dell PE1850 soon, to replace our ancient CVS server > > (still running 4-STABLE). The new machine will ideally run 6.0 and have a > > PERC4e/DC RAID card - the one with battery-backed cache. This is listed as > > supported by amr(4), but I'm wondering how well it actually works in the > > case of a disk failure. Will the driver tell me that disk has failed (a > > syslog message would be enough) or will I have to make a daily trip into > > the server room to check the front panel lights? Presumably it handles > > hot-swapping a replacement drive OK? > > >From what I remember, you will receive status-change kernel messages when > disks disappear, rebuilds start, and so forth. So for most day-to-day > manipulation you should be fine. > > You may want to make sure the auto rebuild option is enabled in the > controller's BIOS since no working control programs from userland are > generally available at this time. That also means you can't create new > volumes at runtime, but thats not so horrible... The sysutils/megarc port appears to work for both status change polling and runtime configuration (at least on a PE800 and a PE2850 that I tested on).