CRC check failed

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ramon Diaz-Uriarte wrote:
> Dear All,
> 
> (Apparently after adding a bunch of large binary files) bzr check
> reports things such as:

...

> bzrs at ameiva:/Disk2/bzr-repositories/RJaCGH$ bzr check
> bzr: ERROR: CRC check failed 3753648892 2779940560

bzr doesn't use CRC's. It uses sha1 checksums, etc.

So what you seem to be encountering is disk-level corruption. If you
want to confirm something like this, on the machine you are getting CRC
errors, try running:

find . -type f -print0 | xargs -0 cat > /dev/null

Which should be trying to read the contents of all the files. My guess
is that one of these will actually trigger the CRC error.

Further, you could try to do this on both sides:

find . -type f -print0 | xargs -0 sha1sum > ../SHA1SUM

If you used rsync to copy things, the data should be identical on both
sides. If you use bzr push/pull/branch, things may not be identical (one
side could have unreferenced texts, slightly different sort order, etc).

So CRC is usually an indication of a disk-crc check failure. Which is do
to your setup. bzr is not generating the error itself. You can also look
in ~/.bzr.log to see if there is any more information available.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFT3irJdeBCYSNAAMRAiHpAJ9PRMGqs2jQO5CAaH7Tnb+VZvQQXACfTgW5
ix9DPfDOtBHxCjnXSITn1p8=
=mdWO
-----END PGP SIGNATURE-----