From: Bryan Donlan <bdonlan@gmail.com>
Date: Wed, 22 Apr 2009 04:21:20 GMT
Subject: Re: What's going on here? Bad repo, no error locally?
Message-ID: <3e8340490904212121q4bf2e25dsf5673bff764895c9@mail.gmail.com>
In-Reply-To: <450196A1AAAE4B42A00A8B27A59278E70ACE053E@EXCHANGE.trad.tradestation.com>

On Tue, Apr 21, 2009 at 8:18 PM, John Dlugosz <JDlugosz@tradestation.com> wrote:
> Developer B runs git fsck --full, gets no errors but one dangling blob.
> Does a push.  No errors.
> Now, on the upstream repo, I run fsck, and find a bunch of danglings (as
> always) and a missing blob.
> Any fetch from that repo will fail, due to that missing blob.
>
> What's going on?  How can I fix his local repository, other than blow it
> away and start over, and copy his current files over and rebuild the few
> commits of interest?

Extract the object on developer B's workstation:
git cat-file blob <object ID>  > blob.dat

Copy it to upstream, then do:
git hash-object -w blob.dat

If all goes well, hash-object will give you back the blob's ID, and
the repository will fsck cleanly again.