Messages in this thread | | | Date | Fri, 18 Jun 1999 17:16:48 +0300 (EET DST) | From | Kastus Shchuka <> | Subject | Re: Massive e2fs corruption with 2.2.9/10? |
| |
On Fri, 18 Jun 1999, Harald Koenig wrote:
> On Jun 18, Linus Torvalds wrote: > > > >[eastep@eastep-3 eastep]$ cat /proc/version > > >Linux version 2.2.10 (eastep@eastep-3.mis.tandem.com) (gcc version > > >egcs-2.91.66 > > > > Does the corruption go away if you use a compiler that is not known to > > miscompile the kernel, eg 2.7.2? > > I had at least two ext2fs corruptions plus two SIGSEGs due to bad bits > in binaries in buffer cache (emacs/mutt) and one full lockup, > all with 2.2.9/2.2.10 compiled with 2.7.2.3 (SuSE 6.1).
Such thing happened to me once, but it traced back to a faulty SIMM. It was in the days of 2.0.2x kernel, computer in question is P166, 64 MB RAM, IWILL motherboard with built-in AIC 7880 SCSI.
At some point I started experiencing problems with copying large (tens of MB) files. Small files (<1MB) copied quite OK. With big ones, the copy just differed from original. What's curious, memtest showed no errors on that computer, Windows also ran without problems with those SIMMs. I replaced faulty SIMMs with ECC ones, and I don't have any such problems for more than a year (knocking on wood)
HTH, Kastus
> > > Harald > -- > All SCSI disks will from now on ___ _____ > be required to send an email notice 0--,| /OOOOOOO\ > 24 hours prior to complete hardware failure! <_/ / /OOOOOOOOOOO\ > \ \/OOOOOOOOOOOOOOO\ > \ OOOOOOOOOOOOOOOOO|// > Harald Koenig, \/\/\/\/\/\/\/\/\/ > Inst.f.Theoret.Astrophysik // / \\ \ > koenig@tat.physik.uni-tuebingen.de ^^^^^ ^^^^^ >
-------------------------------------------- Kastus Shchuka <pike@usis.minsk.by> LAN Manager/SysAdmin ph.: +375-17-217-0481 USIS Minsk fax: +375-17-217-8828
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |