# How to fetch missing pack 10 messages from 2008-04-12 to 2008-04-28. Participants: Jörg Sommer, Peter Baumann, Christian Couder, Shawn O. Pearce, Stephen R. van den Berg, Junio C Hamano. Thread: https://gitlist.dev/t/13074 ## Jörg Sommer, 2008-04-12 12:07 Subject: How to fetch missing pack Message-ID: URL: https://gitlist.dev/e/slrng019fg.nd8.joerg%40alea.gnuu.de ``` Hi, I'm missing a pack. My history of the git repository is broken: % git show --pretty=raw e0fda6ab|head -7 commit e0fda6abd11c567b72f29ec0ee06c541404a9cb7 tree 77a7e4a849bbec646d88ae863f80ea3f519e26bd parent 1ab58e8d6f728cdde0057f7ee88daab3a1c2d06f author Wincent Colaiuta 1196066088 +0100 committer Junio C Hamano 1196109124 -0800 Fix typo in draft 1.5.4 release notes % git log --pretty=oneline e0fda6ab | wc -l 1 % git show e0fda6ab~1|cat fatal: ambiguous argument 'e0fda6ab~1': unknown revision or path not in the working tree. Use '--' to separate paths from revisions Can I somehow tell git fetch to check the whole history for holes and fetch missing packs? Bye, Jörg. -- Der kommt den Göttern am nächsten, der auch dann schweigen kann, wenn er im Recht ist. (Cato; 234–149 v. Chr.) ``` ## Peter Baumann, 2008-04-13 09:41 Subject: Re: How to fetch missing pack Message-ID: <20080413094131.GA9437@xp.machine.xx> URL: https://gitlist.dev/e/20080413094131.GA9437%40xp.machine.xx In-Reply-To: ``` On Sat, Apr 12, 2008 at 12:07:12PM +0000, Jörg Sommer wrote: > Hi, > > I'm missing a pack. My history of the git repository is broken: > % git show --pretty=raw e0fda6ab|head -7 > commit e0fda6abd11c567b72f29ec0ee06c541404a9cb7 > tree 77a7e4a849bbec646d88ae863f80ea3f519e26bd > parent 1ab58e8d6f728cdde0057f7ee88daab3a1c2d06f > author Wincent Colaiuta 1196066088 +0100 > committer Junio C Hamano 1196109124 -0800 > > Fix typo in draft 1.5.4 release notes > % git log --pretty=oneline e0fda6ab | wc -l > 1 > % git show e0fda6ab~1|cat > fatal: ambiguous argument 'e0fda6ab~1': unknown revision or path not in the working tree. > Use '--' to separate paths from revisions > > Can I somehow tell git fetch to check the whole history for holes and > fetch missing packs? > > Bye, Jörg. Try using git fsck --full to check you repo. If you are missing some objects, you could just grab them from another valid repo which still has them. (e.g. copy all packs/objects from the other repo into yours and then do a git-repack -a -d -f) -Peter ``` ## Jörg Sommer, 2008-04-23 20:55 Subject: Re: How to fetch missing pack Message-ID: URL: https://gitlist.dev/e/slrng0v8h8.ujv.joerg%40alea.gnuu.de In-Reply-To: <20080413094131.GA9437@xp.machine.xx> ``` Hi Peter, Peter Baumann wrote: > On Sat, Apr 12, 2008 at 12:07:12PM +0000, Jörg Sommer wrote: >> I'm missing a pack. My history of the git repository is broken: >> % git show --pretty=raw e0fda6ab|head -7 >> commit e0fda6abd11c567b72f29ec0ee06c541404a9cb7 >> tree 77a7e4a849bbec646d88ae863f80ea3f519e26bd >> parent 1ab58e8d6f728cdde0057f7ee88daab3a1c2d06f >> author Wincent Colaiuta 1196066088 +0100 >> committer Junio C Hamano 1196109124 -0800 >> >> Fix typo in draft 1.5.4 release notes >> % git log --pretty=oneline e0fda6ab | wc -l >> 1 >> % git show e0fda6ab~1|cat >> fatal: ambiguous argument 'e0fda6ab~1': unknown revision or path not in the working tree. >> Use '--' to separate paths from revisions >> >> Can I somehow tell git fetch to check the whole history for holes and >> fetch missing packs? >> >> Bye, Jörg. > > Try using git fsck --full to check you repo. If you are missing some > objects, you could just grab them from another valid repo which still has > them. How can I exctract single objects from a pack? > (e.g. copy all packs/objects from the other repo into yours and then do > a git-repack -a -d -f) This didn't work. I've cloned my git repo and copied the pack into packs/objects without the .keep file and removed objects/info/packs. After that I ran repack -a -d -f, but nothing changed. I still can't access the parent of e0fda6ab. What else can I do? Bye, Jörg. -- The social dynamics of the net are a direct consequence of the fact that nobody has yet developed a Remote Strangulation Protocol. (Larry Wall) ``` ## Christian Couder, 2008-04-24 06:01 Subject: Re: How to fetch missing pack Message-ID: <200804240801.13674.chriscool@tuxfamily.org> URL: https://gitlist.dev/e/200804240801.13674.chriscool%40tuxfamily.org In-Reply-To: ``` Le mercredi 23 avril 2008, Jörg Sommer a écrit : > Hi Peter, > > Peter Baumann wrote: > > > > Try using git fsck --full to check you repo. If you are missing some > > objects, you could just grab them from another valid repo which still > > has them. > > How can I exctract single objects from a pack? Please have a look at this: http://git.or.cz/gitwiki/GitFaq#head-ac11406480d09e2df98588e800e41b7256602074 Regards, Christian. ``` ## Shawn O. Pearce, 2008-04-24 06:08 Subject: Re: How to fetch missing pack Message-ID: <20080424060857.GX29771@spearce.org> URL: https://gitlist.dev/e/20080424060857.GX29771%40spearce.org In-Reply-To: <200804240801.13674.chriscool@tuxfamily.org> ``` Christian Couder wrote: > Le mercredi 23 avril 2008, Jörg Sommer a écrit : > > Peter Baumann wrote: > > > > > > Try using git fsck --full to check you repo. If you are missing some > > > objects, you could just grab them from another valid repo which still > > > has them. > > > > How can I exctract single objects from a pack? > > Please have a look at this: > > http://git.or.cz/gitwiki/GitFaq#head-ac11406480d09e2df98588e800e41b7256602074 If you know the name of the objects you are missing, you can make a temporary pack to transfer the list of objects: # at good repo # git pack-objects --stdout save.pack # at bad repo # git index-pack --stdin URL: https://gitlist.dev/e/20080427104704.GA11784%40alea.gnuu.de In-Reply-To: <20080424060857.GX29771@spearce.org> ``` Hi, Shawn O. Pearce schrieb am Thu 24. Apr, 02:08 (-0400): > If you know the name of the objects you are missing, you can > make a temporary pack to transfer the list of objects: > > # at good repo > # > git pack-objects --stdout save.pack > > # at bad repo > # > git index-pack --stdin &1 >/dev/null) echo $outp [ $#outp -eq 0 ] && break cmt=${${outp##* \(}%\)} git cat-file -t $cmt >/dev/null 2>&1 && \ cmt=$(git cat-file commit $cmt |grep '^tree ') echo ${cmt##* } | ssh server cd git\; git pack-objects --stdout | \ git index-pack --stdin >/dev/null done Maybe it helps someone else. :) But now, there's something else broken. % git cat-file commit b63e99500137c913bd801a2f22b6cf88c63b95c5 tree 68a58fb97935f35c6fb7bcbcfed73b1697db000a parent 3f061887c562b20d3ed3d1f764462cf986a1ad12 author Wincent Colaiuta 1195996542 +0100 committer Junio C Hamano 1196019475 -0800 Add "--patch" option to git-add--interactive When the "--patch" option is supplied, the patch_update_cmd() function is … % git cat-file commit 3f061887c562b20d3ed3d1f764462cf986a1ad12 tree 636a0f9c085aac7ba539ef2ace03b3081481891a parent 324ccbd6a09816af830b22b02bbeb06349141849 author Junio C Hamano 1196014210 -0800 committer Junio C Hamano 1196014993 -0800 add -i: Fix running from a subdirectory This fixes the pathspec interactive_add() passes to the underlying … % git rev-parse b63e99500137c913bd801a2f22b6cf88c63b95c5~1 b63e99500137c913bd801a2f22b6cf88c63b95c5~1 fatal: ambiguous argument 'b63e99500137c913bd801a2f22b6cf88c63b95c5~1': unknown revision or path not in the working tree. Use '--' to separate paths from revisions Can someone tell me what I'm doing wrong? > Note that you may need to do this several times; e.g. if you are > missing a tree you won't know what blobs you are missing until > you load the tree and run fsck --full again to parse the tree and > discover the missing blobs. fsck --full reports only dangling objects, no breakage. Bye, Jörg. -- Die zehn Gebote Gottes enthalten 172 Wörter, die amerikanische Unabhängigkeitserklärung 300 Wörter, die Verordnung der europäischen Gemeinschaft über den Import von Karamelbonbons exakt 25911 Wörter. ``` ## Stephen R. van den Berg, 2008-04-27 17:37 Subject: Re: git doesn't finds the parent of a commit (was: How to fetch missing pack) Message-ID: <20080427173731.GA9523@cuci.nl> URL: https://gitlist.dev/e/20080427173731.GA9523%40cuci.nl In-Reply-To: <20080427104704.GA11784@alea.gnuu.de> ``` J?rg Sommer wrote: >% git rev-parse b63e99500137c913bd801a2f22b6cf88c63b95c5~1 >b63e99500137c913bd801a2f22b6cf88c63b95c5~1 >fatal: ambiguous argument 'b63e99500137c913bd801a2f22b6cf88c63b95c5~1': unknown revision or path not in the working tree. >Use '--' to separate paths from revisions >Can someone tell me what I'm doing wrong? I've had similar symptoms when I had circular references in the repository. They're not reported by any of the existing checks, I've submitted a patch (resent it just now) which causes git to check for (and report) circular references when using --topo-order on e.g. git-rev-list. -- Sincerely, srb@cuci.nl Stephen R. van den Berg. ``` ## Junio C Hamano, 2008-04-27 20:18 Subject: Re: git doesn't finds the parent of a commit Message-ID: <7vtzhnf3w5.fsf@gitster.siamese.dyndns.org> URL: https://gitlist.dev/e/7vtzhnf3w5.fsf%40gitster.siamese.dyndns.org In-Reply-To: <20080427173731.GA9523@cuci.nl> ``` "Stephen R. van den Berg" writes: > J?rg Sommer wrote: >>% git rev-parse b63e99500137c913bd801a2f22b6cf88c63b95c5~1 >>b63e99500137c913bd801a2f22b6cf88c63b95c5~1 >>fatal: ambiguous argument 'b63e99500137c913bd801a2f22b6cf88c63b95c5~1': unknown revision or path not in the working tree. >>Use '--' to separate paths from revisions > >>Can someone tell me what I'm doing wrong? > > I've had similar symptoms when I had circular references in the > repository. They're not reported by any of the existing checks, I've > submitted a patch (resent it just now) which causes git to check for > (and report) circular references when using --topo-order on e.g. > git-rev-list. Assuming that we never have SHA-1 hash collisions, the graft mechansim is practically the only way to get yourself into the circular reference situation. Perhaps we should check this circularity when we install grafts instead of special casing the topo-order codepath? How expensive would that alternative approach be? ``` ## Stephen R. van den Berg, 2008-04-27 21:46 Subject: Re: git doesn't finds the parent of a commit Message-ID: <20080427214621.GA30793@cuci.nl> URL: https://gitlist.dev/e/20080427214621.GA30793%40cuci.nl In-Reply-To: <7vtzhnf3w5.fsf@gitster.siamese.dyndns.org> ``` Junio C Hamano wrote: >"Stephen R. van den Berg" writes: >> I've had similar symptoms when I had circular references in the >> repository. They're not reported by any of the existing checks, I've >> submitted a patch (resent it just now) which causes git to check for >> (and report) circular references when using --topo-order on e.g. >> git-rev-list. >Assuming that we never have SHA-1 hash collisions, the graft mechansim is >practically the only way to get yourself into the circular reference >situation. True, I think. >Perhaps we should check this circularity when we install grafts instead of >special casing the topo-order codepath? How expensive would that >alternative approach be? Not practical in its current form. Checking for circular references is O(n) in CPU and memory use relative to the number of commits in the entire repository. Consider: - The proposed check in the topo-order path is very low-cost, it costs a single decrement/increment per commit (and will detect other circular references not caused by the grafts mechanism, if they ever should occur). - If it is being done during the grafts install, then there should be a flag-file (at least), which indicates when the grafts file has changed since the last check. - It could/should be added to git-fsck. -- Sincerely, srb@cuci.nl Stephen R. van den Berg. ``` ## Jörg Sommer, 2008-04-28 14:14 Subject: Re: git doesn't finds the parent of a commit Message-ID: URL: https://gitlist.dev/e/slrng1bmua.25r.joerg%40alea.gnuu.de In-Reply-To: <20080427173731.GA9523@cuci.nl> ``` Hallo, "Stephen R. van den Berg" wrote: > J?rg Sommer wrote: >>% git rev-parse b63e99500137c913bd801a2f22b6cf88c63b95c5~1 >>b63e99500137c913bd801a2f22b6cf88c63b95c5~1 >>fatal: ambiguous argument 'b63e99500137c913bd801a2f22b6cf88c63b95c5~1': unknown revision or path not in the working tree. >>Use '--' to separate paths from revisions > >>Can someone tell me what I'm doing wrong? > > I've had similar symptoms when I had circular references in the > repository. No, this was not my problem. But I found the reason with bisect: .git/shallow. I've started with a shallow clone, but forgot it. Is it possible that git warns about this or ignores the shallow entry if the parent of the commit is available? Bye, Jörg. -- Dein Gesicht wird dir geschenkt. Lächeln musst du selber! (Inga Hermann) ```