On Tue, Dec 17, 2013 at 10:06:20PM -0500, Dale R. Worley wrote:
> Here's the basic backtrace information, and the values of the "size"
> variables, which seem to be the immediate culprits:
> #1 0x00000000004f3633 in xmallocz (size=size@entry=80530636800)
> at wrapper.c:73
> #2 0x00000000004d922f in unpack_compressed_entry (p=p@entry=0x7e4020,
> w_curs=w_curs@entry=0x7fffffffc9f0, curpos=654214694, size=80530636800)
> at sha1_file.c:1797
> #3 0x00000000004db4cb in unpack_entry (p=p@entry=0x7e4020,
> obj_offset=654214688, final_type=final_type@entry=0x7fffffffd088,
> final_size=final_size@entry=0x7fffffffd098) at sha1_file.c:2072
> #4 0x00000000004b1e3f in verify_packfile (base_count=0,
> fn=0x42fc00 <fsck_obj_buffer>, w_curs=0x7fffffffd090, p=0x7e4020)
> at pack-check.c:119
Thanks, that's helpful. Unfortunately the patch I mentioned before won't
help you. The packfile format (like the experimental loose format that my patch
dropped) stores the size outside of the zlib crc. So it has the same
problem: we want to allocate the buffer up front to store the zlib
The pack index does store a crc (calculated when we made or received
the pack) over each object's on-disk representation. So we could check
that, though doing it on every access has performance implications.
The pack data itself also has a SHA-1 checksum over the whole thing. We
should probably do a better job in verify-pack of:
1. Check the whole sha1 checksum before doing anything else.
2. In the uncommon case that it fails, check each individual object
crc to find the broken object (and if none, assume either the
header or the checksum itself is what got munged).
In the meantime, you should be able to do step 1 manually like:
# check first N-20 bytes of packfile against the checksum in the
# final 20 bytes. NB: pretty sure this use of "head" is a GNU-ism,
# and of course you need openssl
for i in objects/pack/*.pack; do
tail -c 20 "$i" >want.tmp &&
head -c -20 "$i" | openssl sha1 -binary >have.tmp &&
cmp want.tmp have.tmp ||
echo >&2 "broken: $i"
git-fsck should be doing this check itself, but I wonder if you are not
making it that far.
> If I understand the code correctly, the object header buffer
> really does encode the size value 0x12c0000000.
If it does, and you do not have an 80G file, then it sounds like you may
have a corrupt packfile.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html