On 12/8/2006 12:48 AM, John Andersen wrote:
The first time I ran md5sum on the file (on the share) was: a72c2c415a81cd7722319004987679f1 backup_ams_1.tar.gz
I rebooted the system, and this time it was: 2a93d60a45712595b6edbbfad5075de3 backup_ams_1.tar.gz
Testing the file with gzip gives this:
gzip -t -v backup_ams_1.tar.gz backup_ams_1.tar.gz: gzip: backup_ams_1.tar.gz: invalid compressed data--crc error
gzip: backup_ams_1.tar.gz: invalid compressed data--length error
The other two systems show the file is ok (file still on share)
gzip -t -v backup_ams_1.tar.gz backup_ams_1.tar.gz: OK
On the Core 2 Duo machine is the kernel seeing it as two processors or one. cat /proc/cpuinfo
It it is seeing it as two, try taskset 0x00000001 gzip -t -v backup_ams_1.tar.gz
It would be interesting it was a core 2 duo problem with 9.3 I have seen one other very minor error when 9.3 could sense two cores but it only exhibited itself in some video processing (MythTV stuff).
I have smp running: orbit:~ # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Pentium(R) D CPU 3.20GHz processor : 1 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Pentium(R) D CPU 3.20GHz orbit:~ # taskset 0x00000001 gzip -t -v backup_ams_1.tar.gz backup_ams_1.tar.gz: gzip: backup_ams_1.tar.gz: invalid compressed data--crc error Herman Knief mentioned a similar problem with a nic, I am going to swap it and see if that makes a difference. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org