David Miller <davem@xxxxxxxxxxxxx> writes: > Indeed I have some serious corruption in my pack file. Just a sanity check; did you run verify-pack on each packfile to validate that suspicion? > I've put this .git dir up at: > > http://vger.kernel.org/~davem/netnext26_git.tar.gz > > if anyone wants to have a look. > > davem@sunset:~/src/GIT/net-next-2.6$ git fsck --full > error: d7d82ec12e618a3152a82f7fbd459ad285403740: invalid sha1 pointer in cache-tree > error: 95381186c4ef9d69f56bb6a9f7334ebe81dd023c: invalid sha1 pointer in cache-tree > error: 6bea4ad565fff638d396298cb6ee7ad6a31ca252: invalid sha1 pointer in cache-tree > error: 3c8b516f2a9634410f6c3a0ee639627d7c4a83d2: invalid sha1 pointer in cache-tree > error: 11f0695e84bc3f83a6eea0d6fb0af2789de351ef: invalid sha1 pointer in cache-tree > error: 7b3c81544c3117201c160af43fa983d68c614e3d: invalid sha1 pointer in cache-tree > error: c9ee57c5c20c3b7a2d7784a4172aef8b34c3a844: invalid sha1 pointer in cache-tree These may only indicate that your .git/index is corrupt but the object database may still be good. We fixed an incorrect "missing object" diagnosis when your repository borrows objects from another repository via the alternates mechanism (check if .git/objects/info/alternates refers to another repository) fairly recently. "Missing objects" could be false alarms. -- 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
