On Thu, 3 Feb 2011, Junio C Hamano wrote: > Nicolas Pitre <nico@xxxxxxxxxxx> writes: > > > However index-pack won't tell you what is broken in the pack when > > corruptions are to be found. > > Yes, but at that point, you are pretty much lost anyway, as the only thing > you can do to salvage salvageable parts of the broken pack, if you still > trust its associated .idx file, is to walk the table of contents and ask > for each individual object; knowing where the .pack or .idx is broken with > the current verify-pack does not help you very much. Well... given that you do have to compare both the generated index and the on-disk index at some point, it is then possible to identify corrupted objects and their location. And with pack index version 2 including a CRC for the packed data, you should be able to tell if the corruption is actually in the pack or in the index (or both if the final pack/index SHA1 sum doesn't match). Nicolas -- 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