From owner-freebsd-current Fri May 29 01:03:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28445 for freebsd-current-outgoing; Fri, 29 May 1998 01:03:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28432 for ; Fri, 29 May 1998 01:03:50 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.8.8/8.8.8) with ESMTP id JAA25222; Fri, 29 May 1998 09:03:45 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <356E6BE1.50B8AEC1@tdx.co.uk> Date: Fri, 29 May 1998 09:03:45 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: tcobb CC: "'freebsd-current@freebsd.org'" Subject: Re: DPT driver fails and panics with Degraded Array References: <509A2986E5C5D111B7DD0060082F32A402FAC2@freya.circle.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG tcobb wrote: > > I have a DPT3344UW/2 running an external 24GB array. OS is FreeBSD > CURRENT circa 5/18/98. I'm running the latest available firmware flash > for the card, all on a P5-233MMX with 128MB RAM. > > Recently I lost a harddrive in my 24GB RAID5 array. The array was > configured with a HOT SPARE which should have allowed it to rebuild > completely online, with no interruption in service (except some minor > slowdowns, perhaps). While the HARDWARE worked well, the DPT DRIVER > failed miserably. One comment (and it's not a flame!) - honestly... ;-) With an array of that size, on a machine that important - did you not test to see what would happen with a failed drive? The only system we have running with RAID at the moment is an NT box on an HP Netserver - but even with that, we pulled a drive to 'see what happened' - and a) make sure it works, and b) note down any important steps to recovering it... We did this before we certified the machines as 24/7 & 'mission critical' (It also shows that even with NT & 'expensive' hardware, theres always stuff they leave out the manual, or have changed on screen, but not in the manual ;-) Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message