From owner-freebsd-hackers Tue Apr 18 12:50:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lodge.guild.ab.ca (lodge.guild.ab.ca [209.91.118.66]) by hub.freebsd.org (Postfix) with ESMTP id ACA4237BB50 for ; Tue, 18 Apr 2000 12:50:45 -0700 (PDT) (envelope-from davidc@acns.ab.ca) Received: from localhost (davidc@localhost) by lodge.guild.ab.ca (8.9.3/8.9.3) with ESMTP id NAA23625; Tue, 18 Apr 2000 13:58:47 -0600 (MDT) (envelope-from davidc@acns.ab.ca) Date: Tue, 18 Apr 2000 13:58:47 -0600 (MDT) From: Chad David X-Sender: davidc@lodge.guild.ab.ca To: Jesper Skriver Cc: Soren Schmidt , freebsd-hackers@FreeBSD.ORG Subject: Re: vinum raid5 panics In-Reply-To: <20000418213554.B32808@skriver.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Apr 2000, Jesper Skriver wrote: > On Tue, Apr 18, 2000 at 09:32:34PM +0200, Soren Schmidt wrote: > > 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. > > RAID5 has problems, I have no problems with RAID0, RAID1 or RAID0+1 ... To be a little more positive, are these problems being addressed, and is there any way that I can help? > > > BTW do you have a fxp netcard pr chance ?? > No, rl0. Chad > I do. > > /Jesper > > -- > Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message