From owner-freebsd-current Fri May 29 03:27:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16594 for freebsd-current-outgoing; Fri, 29 May 1998 03:27:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16463; Fri, 29 May 1998 03:27:30 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id KAA09157; Fri, 29 May 1998 10:27:25 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id MAA25887; Fri, 29 May 1998 12:27:11 +0200 (MET DST) Message-ID: <19980529122551.16212@follo.net> Date: Fri, 29 May 1998 12:25:51 +0200 From: Eivind Eklund To: tcobb , "'freebsd-current@freebsd.org'" , "'freebsd-scsi@freebsd.org'" Subject: Re: DPT driver fails and panics with Degraded Array References: <509A2986E5C5D111B7DD0060082F32A402FAD1@freya.circle.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FAD1@freya.circle.net>; from tcobb on Fri, May 29, 1998 at 05:49:30AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 29, 1998 at 05:49:30AM -0400, tcobb wrote: > > (1) I've had my array (a 2GB RAID1 - personal RAID :-) run in degraded > > mode. This has worked just fine with the driver in -current, with > > the RAID full (of partitions, not data. I can't understand that > > the amount of data should make a difference - the controller > > shouldn't know about this anyway). > > Perhaps the difference is RAID-1 versus RAID-5. This might be so, or there might (I'm probably blaspheming by saying this) be a difference or bug in the handling of degradation from DPT to DPT. What is obvious is only that you're having problems with a particular controller/driver/kernel combination, and that a part of the driver has problems coping with failure somewhere else. I don't think it would be wise to consider the problem to be narrowed down more than that. Now, to be able to debug this as effectively as possible I suggest you/we try to create a list of test-cases that we believe would lock down the problem: Hypothesis 1: The problem occur when using your type of controller, RAID5+HotSpare, "large" amounts of capacity used, your kernel, and a disk fail. Verification: Create above setup, try to fail a disk on it. Now, which parameters to vary depend on whether we can get the above to crash. It might be dependent on having exactly equal disks, too :-( Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message