Re: Recovering from repository corruption

From: Denis Bueno <dbueno@gmail.com>
Date: Jun 10, 2008, 20:03 UTC
Message-ID: <6dbd4d000806101303j4b2032ajc6e004e0a82e4db5@mail.gmail.com>
In-Reply-To: <200806102159.02875.jnareb@gmail.com>

On Tue, Jun 10, 2008 at 15:59, Jakub Narebski <jnareb@gmail.com> wrote:

Show 8 quoted lines

>> Shouldn't these be unreferenced now that I've run filter-branch?
>
> Try to clone this repository (using file:/// pseudo-protocol to force
> transfer of objects instead of hardlinking them), and chek if the
> problem persists in the clone too.  If not, error/missing might be
> in "garbage".
>
> But I'm not sure...

You're onto something:

[dorothy.local /tmp <Tue Jun 10> <16:02:08>] tmp[176] > git clone file:///Volumes/work/identity.fb/ Initialized empty Git repository in /tmp/identity.fb/.git/ remote: Counting objects: 401, done. remote: Compressing objects: 100% (364/364), done. remote: Total 401 (delta 170), reused 0 (delta 0) Receiving objects: 100% (401/401), 233.76 KiB, done. Resolving deltas: 100% (170/170), done.

[dorothy.local /tmp <Tue Jun 10> <16:02:22>] tmp[177] > cd identity.fb/ /tmp/identity.fb

[dorothy.local /tmp/identity.fb <Tue Jun 10> <16:02:24>]
identity.fb[178] > git fsck --full
broken link from  commit 4737fea59fdc8325e09b5206cc7a6ac593446ce3
              to  commit fe431b4b69453ad9207a5528cf9b9d12ef69c988
dangling commit 28aa69aafc8ae901e588f6d341b3e6d3558c6d26
dangling commit 884a8024fbcb9367726abb25f8bb6ac539712d46
missing commit fe431b4b69453ad9207a5528cf9b9d12ef69c988

But I've just substituted one error for another. Are these errors easier to fix?

-- 
                              Denis