Thanks to you and Nicolas for the responses. On Mon, Aug 25, 2008 at 12:01:42PM -0700, Linus Torvalds wrote: > On Mon, 25 Aug 2008, J. Bruce Fields wrote: > > > > Today I got this: > > > > fatal: failed to read delta base object at 3025976 from > > /home/bfields/local/linux-2.6/.git/objects/pack/pack-f7261d96cf1161b1b0a1593f673a67d0f2469e9b.pack > > This is almost certainly due to some corruption. Basically, the call to > "cache_or_unpack_entry()" failed, which in turn is because > 'unpack_entry()' will have failed. > > And since you didn't see any other error, that failure is almost certainly > due to unpack_compressed_entry() having failed. We don't print out _why_ > (which is a bit sad), but the only thing that unpack_compressed_entry() > does is to just "inflate()" the data at that offset. > > So it probably got a zlib data error, or an adler32 crc failure. > > > This has happened once before recently, I believe with a pack that had > > just been created on a recent fetch. (If I remember correctly, this was > > soon after a failed suspend/resume cycle that might have interrupted an > > in-progress fetch; could that possible explain the error?) In that case > > I reset origin/master, deleted a tag or two, and fetched, and the > > problem seemed to be fixed. > > An interrupted fetch shouldn't have caused this, it really should only > happen if you have some actual filesystem data error. Something didn't get > written back correctly, or the page cache isn't coherent (or it got > corrupted by something else like a wild kernel pointer, of course). OK. I seem to recall these pack files are created with something like open write sync close rename ? This is just ext3 with data=writeback on a local laptop disk, ubuntu's 2.6.24-21-generic. Would it be any use trying to look more closely at the pack in connection for any hints? (But with my git repo back I'm happy enough to just forget this for now if there's not anything obvious to try.) --b. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
