Re: [EGIT] Push to GitHub caused corruption

From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date: Aug 14, 2009, 09:19 UTC
Message-ID: <200908141119.49798.robin.rosenberg.lists@dewire.com>
In-Reply-To: <3ae83b000908111552o53189a44h45fc44f124850483@mail.gmail.com>

onsdag 12 augusti 2009 00:52:29 skrev John Bito <jwbito@gmail.com>:

Show 17 quoted lines

> Running git fsck -full on the repo that I pushed from is clean.
> Here's the git fsck -full from GitHub
>        <mojombo>       git fsck --full
>        <mojombo>       broken link from tree
> f4f9ecd1875938baa42467dfd6a8134d75fe5de4 to tree
> 57548924f1eca854dc8db00844f95d3de2c82957
>        <mojombo>       broken link from tree
> f4f9ecd1875938baa42467dfd6a8134d75fe5de4 to tree
> 3d1f74522c3e7c3c03390fae376446fda6eed306
>        <mojombo>       missing tree 3d1f74522c3e7c3c03390fae376446fda6eed306
>        <mojombo>       missing tree 57548924f1eca854dc8db00844f95d3de2c82957
>        <mojombo>       dangling commit ab6ce47159c1eaff0e4bae19291679267de9f669
> 
> The repo on GitHub is back where it was before the push.  I have a
> copy of the corrupt one from GitHub (358MB tar.gz).  If there's
> something I can do that would help to improve JGit/EGit, please let me
> know.

I guess we'd like to try to recreate the problem, unless we see some obvious clue. What does the tres with missing links look like, i.e. f4f9ecd1875938baa42467dfd6a8134d75fe5de4.

On the recreation side we'd probably need to recreate a repo that looks somewhat like the github repo before the crash. We can do that by taking a copy of your existing (good) repo, reset branches and clone it. Then push from yet another copy and hopefully it will blow up again.

Can we be sure it wasn't corrupt before the jgit push? Did f4f9ecd1875938baa42467dfd6a8134d75fe5de4 exist before the push or was it new?

-- robin