Re: 2.6.21-git10/11: files getting truncated on xfs? or maybe an nlink problem?

[Jeremy Fitzhardinge <jeremy@goop.org>]

David Chinner wrote:
> Ok, so most of the of the integrity errors are processed by an
> error like this:
>
> drivers/scsi/sata_sil24.c index contains -98 extra bytes
> unpacking file drivers/scsi/sata_sil24.c 5715cdfceaca: Error -5 while decompressing data
>
> That's an -EIO and not a normal error to report. Are there any
> errors in dmesg or syslog corresponding to this?
>   

No, that's an error code from zlib:
#define Z_BUF_ERROR    (-5)

I think it means it got a truncated buffer while decompressing.

> The errors tend to imply problems decompressing and patching files,
> not that truncates are occurring once the files have been patched.
> Can you check that what is being pulled from the repository is correct
> before it gets uncompressed?
>   

The hg verify checks the integrity of all the files by decompressing
them and making sure their sha1 hashes are correct.  The fact that the
first hg verify passed is a very strong check that the whole repo's
integrity is sound, both in structure and content.  The second failing
hg verify's messages are all related to truncation.  I haven't checked
this comprehensively, but in every instance I've checked the files are
identical up to the truncation point.  All the error messages are
consistent with pure truncation, not content differences or IO errors.

    J