On 7/18/2015 3:11 PM, Pádraig Brady wrote:
On 18/07/15 19:38, Leslie Rhorer wrote:
Package: coreutils
Version: 8.23-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
CRC checks on large files often return variable values. I have tried several
different CRC check utilities, md5sum, md6sum, sha56sum, etc., and they all
exhibit the same behavior. Multiple runs of the utility on a given file more
often than not will return different values for many or all of the attempts. I
have only noticed the effect on large files, but I cannot say with authority it
only happens on large files. I noticed the effect when checking file integrity
between identical files on two different systems. The backup server is running
Squeeze, and checks on the files of that system are consistent, but when
comparing the CRC between that system and the primary, which is running Jessie,
the checks often failed. At first I of course thought this indicated file
corruption on one server or the other, beut when I started investigating, I
discovered sometimes the results were different on the two systems and
sometimes the same. At that point I discovered it was only!
th!
e machine running Jessie that was producing inconsistent results. At first I
thought I was having problems with the file system (and indeed I am, as it
happens), but when I copied one of the large files over to a different file
system, the problem perissts. One is an XFS file system (the one having the
problems) and the other is an Ext4 file system.
Note this impacts a great many very important procedures and utilities,
including my backup and compare strategy using rsync, file systems checks, etc.
RAID-Server:/# sha256sum "/RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014,
MAXHD).mp4"
b2e15ca178832e9f12a4823c583eefb2028cec9f7c45f36ea9dfa2297c904d6d
/RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4
RAID-Server:/# sha256sum "/RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014,
MAXHD).mp4"
eb3067b250d5d16e1d5d3f2b328001be91c4e5107a14e0010940acdab6584f2b
/RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4
RAID-Server:/# sha256sum "/RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014,
MAXHD).mp4"
6eddb4174b49e9bac741070559ad159acaa39a404a1b75c395d716910e5c81ef
/RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4
The inconsistent results are restricted to the Jessie system?
I believe so, yes. I just booted up another Jessie system and copied
over the file mentioned above, and it worked 3 times in a row. Although
not proof positive, it suggests the issue is limited to this machine.
I'd run memtest given results like that.
I'm not able to reboot at the moment. I'll give it a look later, but
memtester shows no errors. Of course that doesn't verify all the memory.
Also I'd verify a separate checksum implementation.
I don't think debian configures coreutils --with-openssl
so this should be independent:
openssl md5 largefile
RAID-Server:/tmp/temp# openssl md5 "Abyss, The (Recorded Thu Sep 11,
2014, MAXHD).mp4"
MD5(Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4)=
fa54d754e0c51653d71d2419a26e18de
RAID-Server:/tmp/temp# openssl md5 "Abyss, The (Recorded Thu Sep 11,
2014, MAXHD).mp4"
MD5(Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4)=
6886fc9d69c5d1d3685ed158626ce563
thanks,
Pádraig.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
