Bug 831636 - Intermittent data corruption after upgrade to fedora 17
Summary: Intermittent data corruption after upgrade to fedora 17
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-13 13:40 UTC by Adrian Reber
Modified: 2012-09-11 18:38 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-09-11 18:38:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adrian Reber 2012-06-13 13:40:47 UTC
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.

Comment 1 Adrian Reber 2012-06-18 19:50:58 UTC
It seems it now also has happened on my notebook. Copying image files from a SD card to the hard disk created corrupted JPEGs.

Comment 2 Justin M. Forbes 2012-09-11 16:00:06 UTC
Is this still happening with 3.5.3 kernels in updates?

Comment 3 Adrian Reber 2012-09-11 18:38:47 UTC
No, this has been fixed sometimes during 3.4.x


Note You need to log in before you can comment on or make changes to this bug.