From owner-freebsd-stable@FreeBSD.ORG Fri Feb 25 11:29:38 2005 Return-Path: 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 B5A9116A4CF for ; Fri, 25 Feb 2005 11:29:38 +0000 (GMT) Received: from dglawrence.com (dsl-230-156.ipns.com [209.210.230.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C94C43D54 for ; Fri, 25 Feb 2005 11:29:38 +0000 (GMT) (envelope-from dg@dglawrence.com) Received: from opteron.dglawrence.com (localhost [127.0.0.1]) by dglawrence.com (8.13.3/8.13.1) with ESMTP id j1PBTZuh009646 for ; Fri, 25 Feb 2005 03:29:35 -0800 (PST) (envelope-from dg@dglawrence.com) Received: (from dg@localhost) by opteron.dglawrence.com (8.13.3/8.13.1/Submit) id j1PBTZiN009645 for freebsd-stable@freebsd.org; Fri, 25 Feb 2005 03:29:35 -0800 (PST) (envelope-from dg@dglawrence.com) Date: Fri, 25 Feb 2005 03:29:35 -0800 From: "David G. Lawrence" To: freebsd-stable@freebsd.org Message-ID: <20050225112935.GC3258@opteron.dglawrence.com> References: <20050223204202.31797.qmail@web11604.mail.yahoo.com> <421DFC73.7060602@cs.tu-berlin.de> <013301c51a8b$ed2ad230$0300000a@Uzi> <7f6570e5997b376fb8f75d812d386264@elhombre.us> <6.2.1.2.0.20050224153015.02be6df0@64.7.153.2> <20050224233122.GD41951@e-Gitt.NET> <20050225083339.GA5014@aoi.wolfpond.org> <20050225110543.GA70464@e-Gitt.NET> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050225110543.GA70464@e-Gitt.NET> Subject: Re: SATA RAID Support X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 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, 25 Feb 2005 11:29:38 -0000 > Under heavy load (I/O load on the disks constantly over 200 tps, average > at about 250 tps, peaks over 600 tps) a random drive disconnects from > the RAID 10. After removing the drive from the config and rescanning the > bus, the drive does not show up anymore. The only way to get the drive > back is to unplug the drive (or switch the computer off, so that power > is removed). After that there is no problem to rebuild the RAID with > the drive. > > -> It's not reproducable. The error occurs under high load, sometimes > three times a week, sometimes it does not happen in 3 months. > > -> It happens only with the Raptors. > > -> It's always a random drive, there's no drive, that disconnects more > often This sounds like a bug in the drive firmware. Did you look into any firmware updates from Western Digital? It's possible that the 3ware controllers push the drives a bit harder and expose problems that wouldn't show up at slightly lower TPS rates. We (TeraSolutions and Download Technologies) have deployed the 3ware 9500S controllers extensively and haven't seen any problems with the 7k250 and 7k400 series Hitachi drives that we use with them. One of the cool things about the 3ware controllers is that they will automatically do bad block reassignment by first recovering the data from the redundancy, issuing a block reassignment to the drive, and then writing the recovered block back out to the new (reassigned) block. This may seem pretty basic for RAID, but many controllers we've tested actually don't do this. -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 TeraSolutions, Inc. - http://www.terasolutions.com - (888) 346 7175 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities.