I believe I might have hit this bug. I copied a 3GB iso file from NFS to a local EXT4 partition and noticed that the sha1sum is off (I only checked because the burned dvd behaved strange). I copied the file again and then it got the correct sum.
I still have both files and will keep them for a while in case they can be of help in analyzing the issue.
I just finished a full memtest86 run and it passed fine.
Some more info:
- Upgraded from jaunty, the fs was created as ext4 by jaunty
- Kernel: 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux
- SATA hdd, no SSD
- Nothing related in dmesg
- Booted from karmic live disc and ran e2fsck /dev/sda1, no errors found.
- ('e2fsck -n /dev/sda1' on mounted fs does report errors, but I assume that is because it is mounted?)
Later I updated the kernel and I have 2.6.31-15-generic #50 running now and copied a number of 3gb isos again. Now again one of the 4 files has an incorrect hash. So this update did not fix the bug, but I did not see anything related in the change log anyway.
Scott, what kernel versions are you referring to, that you cannot reproduce this anymore?
Let me know if I can provide any further information.
I believe I might have hit this bug. I copied a 3GB iso file from NFS to a local EXT4 partition and noticed that the sha1sum is off (I only checked because the burned dvd behaved strange). I copied the file again and then it got the correct sum.
I still have both files and will keep them for a while in case they can be of help in analyzing the issue.
I just finished a full memtest86 run and it passed fine.
Some more info:
- Upgraded from jaunty, the fs was created as ext4 by jaunty
- Kernel: 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux
- SATA hdd, no SSD
- Nothing related in dmesg
- Booted from karmic live disc and ran e2fsck /dev/sda1, no errors found.
- ('e2fsck -n /dev/sda1' on mounted fs does report errors, but I assume that is because it is mounted?)
Later I updated the kernel and I have 2.6.31-15-generic #50 running now and copied a number of 3gb isos again. Now again one of the 4 files has an incorrect hash. So this update did not fix the bug, but I did not see anything related in the change log anyway.
Scott, what kernel versions are you referring to, that you cannot reproduce this anymore?
Let me know if I can provide any further information.