From owner-freebsd-current Fri May 29 01:12:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29686 for freebsd-current-outgoing; Fri, 29 May 1998 01:12:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29661 for ; Fri, 29 May 1998 01:12:37 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Fri, 29 May 1998 04:12:01 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FACD@freya.circle.net> From: tcobb To: "'Karl Pielorz'" Cc: "'freebsd-current@freebsd.org'" Subject: RE: DPT driver fails and panics with Degraded Array Date: Fri, 29 May 1998 04:12:00 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Karl Pielorz [mailto:kpielorz@tdx.co.uk] > Sent: Friday, May 29, 1998 4:04 AM > To: tcobb > Cc: 'freebsd-current@freebsd.org' > Subject: Re: DPT driver fails and panics with Degraded Array > > > 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... ;-) No flame taken ;) > With an array of that size, on a machine that important - did > you not test > to see what would happen with a failed drive? Actually, we did that when we first implemented this array last November. Yanked a drive. The hardware screamed (beeped like a banshee), the system kept operating then but wasn't under any real load. Despite pre-certification testing, something will be different when you have a failure in production. The difference in our case, I'm guessing, was that the array is now 60-75% full, and the OS version is different, and the system was under heavy access load, too. The original driver was an over-hacked version stuffed into 2.2.2, the newest driver IS better integrated, and actually faster, but obviously unable to handle the under-load failure situation in exactly the way we had it happen. -Troy Cobb Circle Net, Inc. http://www.circle.net > 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