From owner-freebsd-hackers Tue Aug 26 23:52:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA14524 for hackers-outgoing; Tue, 26 Aug 1997 23:52:14 -0700 (PDT) Received: from tornado.netspace.net.au (mheath@netspace.net.au [203.10.110.110]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA14517 for ; Tue, 26 Aug 1997 23:52:11 -0700 (PDT) Received: (from mheath@localhost) by tornado.netspace.net.au (8.8.5/8.7.1) id QAA21442; Wed, 27 Aug 1997 16:53:06 +1000 (EST) Date: Wed, 27 Aug 1997 16:53:05 +1000 (EST) From: Mark Heath To: Tom Samplonius cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Status of the following bugs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 26 Aug 1997, Tom Samplonius wrote: > > > The mangled entry error generally means that the filesystem is > corrupted. You need to reboot and run fsck until it comes up clean. This has been done a number of times. And the filesystem has even re newfs'd a couple of times. Aparently its is caused by a vnode race condition. I dont know much else about the bug. > > The other errors are unfamilar. Probably memory. I bet you don't have > parity memory do you? I wasn't aware that you could get Parity EDO ram. Im not a hardware guru. > I use parity simms, and a motherboard that supports ECC. It is the only > way to go when using large memory configurations. The only bios option I can find is: DRAM are 64 (not 72) bits wide Data Integrity (PARITY): enabled/disabled option. Is this relevant? -- mark heath - Netspace Online Systems. http://www.netspace.net.au/ :wq