Hal,
I've got a similar thing happening to a PPro 200 running RH 6.1
The machine is constantly bellyaching about crash this bad inodes
that... memtest86 says Nada... nothing wrong with the system. If
you can eventually figure out what is wrong with your system, please
let me know... I'd love to fix this sucker back up. I have to reboot
it at least three times a week to clear up problems.
Bill Ward
-----Original Message-----
From: Hal Burgiss [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 01, 2000 11:57 AM
To: [EMAIL PROTECTED]
Cc: recipient.list.not.shown; @nswcphdn.navy.mil
Subject: Re: umounting / for fsck
On Mon, May 01, 2000 at 10:12:55AM -0500, Bill Carlson wrote:
> On Mon, 1 May 2000, Hal Burgiss wrote:
> >
> > Apr 30 04:24:43 localhost kernel: EXT2-fs warning (device ide0(3,4)):
> > ext2_free_inode: bit already cleared for inode 191777
>
> Hal,
>
> I've seen errors like these before, 2 or 3 years ago. The problem
> turned out to be flakey RAM, you might want to test that right
> away...
Thanks, I'll give that a shot. Curious that e2fsck does not want to
fix this (at least permaneantly), and seems to be the same inodes
everytime.
memtest86?
--
Hal B
[EMAIL PROTECTED]
--
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.