From owner-freebsd-stable@FreeBSD.ORG Fri Jan 13 17:12:47 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 28B3C16A41F for ; Fri, 13 Jan 2006 17:12:47 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BE9743D46 for ; Fri, 13 Jan 2006 17:12:46 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id k0DHCVNS055588; Fri, 13 Jan 2006 12:12:31 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Doug Ambrisko Date: Fri, 13 Jan 2006 12:12:15 -0500 User-Agent: KMail/1.6.2 References: <200601131659.k0DGxmob083744@ambrisko.com> In-Reply-To: <200601131659.k0DGxmob083744@ambrisko.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200601131212.19465.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1240/Fri Jan 13 11:57:12 2006 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Scott Mitchell , Vivek Khera , 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, 13 Jan 2006 17:12:47 -0000 On Friday 13 January 2006 11:59 am, Doug Ambrisko wrote: > Jung-uk Kim writes: > | On Thursday 12 January 2006 07:41 pm, Doug Ambrisko wrote: > | > Scott Mitchell writes: > | > | > I did find a program > | > | > posted to one of the freebsd lists called 'amrstat' that I > | > | > run nightly. It produces this kind of output: > | > | > > | > | > Drive 0: 68.24 GB, RAID1 > | > | > optimal > | > | > > | > | > If it says "degraded" it is time to fix a drive. You just > | > | > fire up the lsi megaraid tools and find out which drive it > | > | > is. > | > > | > This is probably a faily good scheme. Caveat is that you can > | > have a "optimal" RAID that is broken :-( > | > | That's lame. Under what condition does it happen, do you know? > > Running RAID 10, a drive was swapped and the rebuild started on the > replacement drive. The rebuild complained about the source drive > for the mirror rebuild having read errors that couldn't be > recovered. It continued on and finished re-creating the mirror. > Then the RAID proceeeded onto a background init which they normal > did and started failing that and re-starting the background init > over and over again. The box changed the RAID from degraded to > optimal when the rebuild completed (with errors). Do a dd of the > entire RAID logical device returned an error at the bad sector > since it couldn't recover that. The RAID controller reported an I/O > error and still left the RAID as optimal. > > We reported this and where told that's the way it is designed :-( > Probably the spec. is defined by whatever the RAID controller > happens to do versus what make sense :-( > > So far this has only happened once. Changing firmware did not > help. Similar thing happened to me once or twice (with RAID5) and I thought it was just a broken controller. If the culprit was design, it IS really lame. :-( > Doug A. > > PS. sorry for the null email before this. Hit the wrong key. No need to be sorry. I made the same mistake again. ;-) Thanks for the info, Jung-uk Kim