Messages in this thread | | | Date | Thu, 18 Jun 1998 11:55:40 -0400 (EDT) | From | "Richard B. Johnson" <> | Subject | Re: Corruption in 2.1.106 |
| |
On Fri, 19 Jun 1998, Alan Cox wrote:
> 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. I've been reporting this. My guess is that something is not being completely written to the disk during dismount (umount). But if you see memory corruption (which I don't see), it may be something entirely different. I'm still using 2.1.105, but with these patches:
ext2_trunc105-patch mmap_105-patch nfsd_105-patch
Cheers, Dick Johnson ***** FILE SYSTEM MODIFIED ***** Penguin : Linux version 2.1.105 on an i586 machine (66.15 BogoMips). Warning : It's hard to remain at the trailing edge of technology.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |