We are running a relatively big mirror server (20TB, 64GB RAM) and have updated from Fedora 14 to Fedora 17. Since running Fedora 17 we have reports of data corruption after the download. It does not happen always but only sometimes. It is hard which part should be blamed so I selected the kernel. Running md5sum on the disk gives always the correct checksum. After downloading the file there are different checksums: root@rhlx01:/ftp/ubuntu/dists/lucid/main/binary-amd64 # md5sum Packages.bz2 f9f2c23454c2e8d6b87cc65fc475900f Packages.bz2 wget http://ftp-stud.hs-esslingen.de/ubuntu/dists/lucid/main/binary-amd64/Packages.bz2 # three times $ md5sum Packages.bz2* fc45e437a1680b7955c2b713d5f5b764 Packages.bz2 f9f2c23454c2e8d6b87cc65fc475900f Packages.bz2.1 f9f2c23454c2e8d6b87cc65fc475900f Packages.bz2.2 We are running following kernel: kernel-3.4.0-1.fc17.x86_64 Our RAIDs are connected over Fibre Channel. One is using the ql2xxx driver and the other is using the mptfc driver. I will try to downgrade to 3.3.4-5.fc17 to see if that helps.
It seems it now also has happened on my notebook. Copying image files from a SD card to the hard disk created corrupted JPEGs.
Is this still happening with 3.5.3 kernels in updates?
No, this has been fixed sometimes during 3.4.x