If I remember the original post, he has a SCSI Quantum Fireball on which he was
seeing these strange corruption problems. I can report very similar problems
under 2.0.35, particularly under tight memory. I've since moved that machine
to the 2.1.x tree, and the problems are no more. FWIW, however, the tar/gzip
errors were generally repeatable, and a reboot solved the problem. After a
couple of reboots, however, fsck reported some fairly serious errors. Sounds
like classic memory corruption. Non-overclocked Pentium 166 UP, 430HX chipset.
SCSI host adapter: Adaptec AHA2940U. All problems happened only on the Fireball.
Joel
17[jde@rasta scsi]Z% cat /proc/scsi/scsi 9:07
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST32430N Rev: 0594
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: QUANTUM Model: FIREBALL_TM3200S Rev: 300N
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: CONNER Model: CTMS 3200 Rev: 7.15
Type: Sequential-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 05 Lun: 00
Vendor: IOMEGA Model: ZIP 100 Rev: E.08
Type: Direct-Access ANSI SCSI revision: 02
-
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.altern.org/andrebalsa/doc/lkml-faq.html