Date: Wed, 27 Aug 1997 16:53:05 +1000 (EST) From: Mark Heath <mheath@netspace.net.au> To: Tom Samplonius <tom@sdf.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Status of the following bugs Message-ID: <Pine.SOL.3.91.970827162317.22773G-100000@tornado.netspace.net.au> In-Reply-To: <Pine.BSF.3.95q.970826231236.28747C-100000@misery.sdf.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SOL.3.91.970827162317.22773G-100000>