Date: Wed, 27 Aug 1997 08:25:41 -0700 (PDT) From: Tom Samplonius <tom@sdf.com> To: Mark Heath <mheath@netspace.net.au> Cc: freebsd-hackers@freebsd.org Subject: Re: Status of the following bugs Message-ID: <Pine.BSF.3.95q.970827081741.294A-100000@misery.sdf.com> In-Reply-To: <Pine.SOL.3.91.970827162317.22773G-100000@tornado.netspace.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 27 Aug 1997, Mark Heath wrote: > 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. Possibly, but I haven't seen this panic in a long time. At one point, fsck would not fix some file system problems, so every time a certain directory was touched, the server would panic. fsck was fixed though. Strange thing, is that you are getting three different panics. > > 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. Parity memory just has an extra bit per byte. It is hard to get parity edo. But if you can't, just use FP. You only lose maybe 3% memory performance, probably less. > > 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? It is telling you that your RAM is 64bit wide, not 72bit, so you can't support parity. BTW, memory corruption also causes file system corruption. Think about what happens if you get a single bit error in some portion of memory that is being written to disk... it corrupts your disk too! BTW, I have a similar news setup. A PPro 200 with 192MB of RAM, and 11 disks, running 2.2-stable, and it doesn't panic. > -- mark heath - Netspace Online Systems. http://www.netspace.net.au/ > :wq > > > Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.970827081741.294A-100000>