Corruption in 2.1.106

Trever Adams (highlander@teleteam.net)
Fri, 19 Jun 1998 17:49:08 -0500


> Im having fun trying to pin this down for definite as Im using new hardware
> but it definitely appears that 2.1.105 (and + patches) is stablish on my
> hardware. 2.1.106 (with or without patches) is corrupting the file system -
> and normally in ways that dont show up until you force an fsck by hand
> when you find bad blocks, duplicate blocks and interesting crap lurking
> on the wrong parts of the disk.
>
> Are other people seeing 2.1.106 corrupting disks and memory on x86 ?
>
> Alan
>

Yes sir, I have. First it started as not unmounting things (crashes
with sound you know). After a time, I would erase things, df would show
a gain in free space. Within a short period of time (no new info being
written to that disk) it would show 100% used. I would reboot, go into
single user mode, mount read-only, and force a check, no problems that
it would find.

As I wanted to give RH 5.1 a shot I just backed up my important data and
blew away it and my main windows drive (thank heavens I don't use it
much anymore... less every time something cool comes out to replace a
program I need).

As for memory corruption, I don't believe I have seen that, just very
strange disk corruption.

Trever Adams
highlander@teleteam.net (please don't post this to a public newsgroup!)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu