Brad Shelton wrote:
On Wed, Feb 09, 2000 at 05:43:05PM -0500, Paul W. Abrahams wrote:
"Paul W. Abrahams" wrote earlier:
Here is the text of a message I sent to the maintainter of the ext2fs filesystem. I think it would be of interest to this group, especially if anyone here has had a similar experience.
1. Summary: Ext2fx implosion when RAM added
I won't repeat the previous message again, but I've run a memory tester (memtest86) and think it's unlikely the memory is at fault. And all the surface testing I've done makes it unlikely the disk is at fault.
I'm wondering if possibly there might be a subtle bug in the unmounting procedures that cause the filesystem to become unsynchronized in certain (rare) environments, leaving essential data in a cache that's wiped out on shutdown.
Hmmm. Did I miss it, or did you tell us you weren't using the append="MEM=128M" lilo boot statement?
Just curious to see if that's involved in your predicament.
I never heard of the MEM=128M statement. Is it supposed to be necessary? If so, it's another of those magical incantations. Paul Abrahams -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/