Date: Fri, 29 May 1998 11:43:01 +0200 From: Eivind Eklund <eivind@yes.no> To: tcobb <tcobb@staff.circle.net>, "'freebsd-current@freebsd.org'" <freebsd-current@FreeBSD.ORG>, "'freebsd-scsi@freebsd.org'" <freebsd-scsi@FreeBSD.ORG> Subject: Re: DPT driver fails and panics with Degraded Array Message-ID: <19980529114301.44319@follo.net> In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FAC2@freya.circle.net>; from tcobb on Thu, May 28, 1998 at 10:49:23PM -0400 References: <509A2986E5C5D111B7DD0060082F32A402FAC2@freya.circle.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 28, 1998 at 10:49:23PM -0400, tcobb wrote:
> I believe that the DPT DRIVER is not correctly sensing that the array is
> okay, even though it is in degraded mode, and incorrectly returns
> sector/MB values which panic the kernel. I don't recommend depending on
> the proper operation of this driver for your High-Availability needs.
I have an older DPT, but I still want to add my experiences to the
above:
(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).
(2) The DPT controller on this has reported alternating wrong sense of
the disk setup to the BIOS. This is obviously NOT a driver
problem.
As for your problems, I'm sorry to hear about them, but have no idea
how to fix it. I've had none of the problems you have :-(
Eivind.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980529114301.44319>