From owner-freebsd-hackers Tue Apr 18 12:32:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C832237B9F4 for ; Tue, 18 Apr 2000 12:32:46 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA01404; Tue, 18 Apr 2000 21:32:34 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004181932.VAA01404@freebsd.dk> Subject: Re: vinum raid5 panics In-Reply-To: from Chad David at "Apr 18, 2000 10:22:01 am" To: davidc@acns.ab.ca (Chad David) Date: Tue, 18 Apr 2000 21:32:34 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Chad David wrote: > I just put together a 5 disk raid5 system using > vinum on 4.0 from last Wed., and I am experiencing > random panics. I can force the panic by working on > the filesystem, but sometimes just having it mounted > kills the machine. > > I compiled a debug kernel, and got a crash dump, but > I am not an expert at debugging crash dumps, so any > advice would be appreciated. > > Instead of dumping out fifty pages of kernel and > hardware config could anyone who is working on this > let me know what would be helpful... I bet you see the same problem as others do.... In my book vinum on 4.0 is plain broken. If its an option for you, vinum under -current works better but its still far from stable. BTW do you have a fxp netcard pr chance ?? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message