On 07/06/12 11:20, Vincent Lefevre wrote: > Actually these are only MD5 errors (from my own checks), no > "bunzip2: Data integrity error when decompressing" errors.
Couldn't you pipe the uncompressed data directly into your integrity checking program? Without using bzip2/bunzip2 or any other compressors at all? > And "bunzip2 -t mpfr-0-8207.bz2" in a loop never fails. If the .bz2 file is too small (<<80GiB), this test may not be reliable (it would likely be read from disk only once, if at all, then sit in memory cache for all test iterations). My guess right now is that a problem with the fileserver causes either of these scenarios to happen: (1) data is read from fileserver with errors > piped to bzip2 > saved to fileserver > read back OK from fileserver > decompresses without error > MD5 sums in the data don't verify (2) data is read OK from fileserver > piped to bzip2 > saved to fileserver > read back from fileserver with errors > CRC errors from bunzip2 Since compressed data takes up some fraction of the space of uncompressed data, I expect that (1) would be observed proportionally more often than (2). Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
