Messages in this thread | | | Date | Fri, 19 Jun 1998 17:29:01 +0200 (MET DST) | From | Cyrille Chepelov <> | Subject | Re: Corruption in 2.1.106 |
| |
On Fri, 19 Jun 1998, Alan Cox wrote:
> Are other people seeing 2.1.106 corrupting disks and memory on x86 ?
Got something strange in that vein yesterday --- tried to compile Python 1.5.1, found about a kilobyte of VisualC++ makefiles (with nifty ^M at the end of every line <grin/>), approximately 512 bytes away from the beginning of a C file (Objects/abstract.c if that matters, which I doubt).
The device was a 640-Mb Magneto-Optic Drive (2048 bytes/sector, hard sectored), FS was ext2.
Immediately umounted the filesys, ran "init 1", fsck'ed. Got a few errors in the volume bitmap, then rebooted, remounted, rm -rf'ed the Python directory, started over at tar -zxf stage, this time compilation (of Python) went fine.
I didn't complain at first, because I have an old Stepping B K6-200MMX, and first wanted to check whether that was to happen again or not.
Good luck...
-- Cyrille
------------------------------ Zog Zog
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |