Skip to contentSkip to conversation

Assertion failure wth ext3 on standard Redhat 7.2 kernel

DISCUSSION Robert Lowery 1 participant 1 message Nov 9, 2001

lore
Share & tools
lore
#0 lore raw

Hi Andrew,

Quoted 5 lines

ext3 downloads are currently running at 1,200 per day plus an unknown number of Red Hat users, and you're the first to report this one. So it's going to be something odd. It _could_ be bad hardware, but if it's always failing in the same way, that sounds unlikely.

I too thought bad hardware. I will try removing the extra 64M I added recently and see if it still happens.

Quoted 2 lines

Could you please force a `fsck' against the fs, let us know the outcome?

After a crash I say Y (within 5 seconds) on reboot to run an fsck and there are usually corrupted files from what I was doing when it crashed. Eg I was running rpm -Uvh kernel-sources... and some files in /usr/src/linux... were corrupted.

Quoted 1 line

Also, a ksymoops trace of the oops output would be most useful.

How do I do this when the box has crashed? I can manually write down the oops, but then what do I do? Can I manually look up System.map to get what you need?

Quoted 3 lines

It looks like memory corruption of some form - a structure member has an impossible value. Are you using any less-than-mainstream device drivers in that box?

I agree. Everything is pointing to the new memory, even though I successfully ran memtest86 for 10 hours.

Thanks

-Robert