"R. Tyler Ballance" <tyler@xxxxxxxxx> writes: > On Wed, 2009-01-07 at 00:16 -0800, Junio C Hamano wrote: >> "R. Tyler Ballance" <tyler@xxxxxxxxx> writes: >> >> > Unfortunately it doesn't, what I did notice was this when I did a `git >> > status` in the directory right after untarring: >> > tyler@grapefruit:~/jburgess_main> git status >> > # >> > # ---impressive amount of file names fly by--- >> > # ----snip--- >> > ... >> > Basically, somehow Git thinks that *every* file in the repository is >> > deleted at this point. >> >> That makes me suspect that your .git/index file is corrupt. > > Would this be tied to the corrupted pack file issue, or separate. If you have perfectly good set of packs, if your index is corrupt you may see "everything deleted", so in that sense it is independent. As Linus's earlier conjecture was that this is related to some sort of disk/cache corruption, I wouldn't be surprised if such a failure hit packs and the index file indiscriminatingly. So in that sense they are related. I think "git ls-files" (before doing anything else, such as resetting, of course) would report that the index is corrupt, if that is indeed the case. -- 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
