From: Jakub Narebski <jnareb@gmail.com>
To: "Denis Bueno" <dbueno@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Recovering from repository corruption
Date: Tue, 10 Jun 2008 22:14:40 +0200 [thread overview]
Message-ID: <200806102214.40805.jnareb@gmail.com> (raw)
In-Reply-To: <6dbd4d000806101303j4b2032ajc6e004e0a82e4db5@mail.gmail.com>
On Tue, 10 Jun 2008, Denis Bueno wrote:
> On Tue, Jun 10, 2008, Jakub Narebski <jnareb@gmail.com> wrote:
>> Denis Bueno wrote:
>>>
>>> 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?
Please remember that in such clone you _don't_ have grafts info (unless
you copy it manually), so it is a good test if you correctly rewrote
history using git-filter-branch. So take a look at history in your
clone using gitk or some similar tool.
In the history you mentioned:
...---a---* b---c---d---* e---...
\ / \ /
\-X-/ \---/
you should rewritr from 'a'=='X^' to, and including 'e' (and not only
from 'd').
But if it is not the case I'm afraid I wouldn't be able to offer any
further insight...
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-06-10 20:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 17:26 Recovering from repository corruption Denis Bueno
2008-06-10 17:55 ` Jakub Narebski
2008-06-10 19:38 ` Denis Bueno
2008-06-10 19:59 ` Jakub Narebski
2008-06-10 20:03 ` Denis Bueno
2008-06-10 20:14 ` Jakub Narebski [this message]
2008-06-10 20:35 ` Denis Bueno
2008-06-10 20:23 ` Linus Torvalds
2008-06-10 20:28 ` Denis Bueno
2008-06-10 21:09 ` Linus Torvalds
2008-06-10 21:22 ` Denis Bueno
2008-06-10 21:48 ` Linus Torvalds
2008-06-10 22:09 ` Denis Bueno
2008-06-10 22:25 ` Tarmigan
2008-06-10 22:41 ` Denis Bueno
2008-06-10 22:45 ` Linus Torvalds
2008-06-10 23:00 ` Linus Torvalds
2008-06-11 0:43 ` Nicolas Pitre
2008-06-11 1:39 ` Linus Torvalds
2008-06-11 1:47 ` Nicolas Pitre
2008-06-10 21:27 ` Denis Bueno
2008-06-10 22:52 ` Junio C Hamano
2008-06-11 23:21 ` To graft or not to graft... (Re: Recovering from repository corruption) Stephen R. van den Berg
2008-06-11 23:34 ` Jakub Narebski
2008-06-11 23:39 ` Linus Torvalds
2008-06-12 7:14 ` Johan Herland
2008-06-12 7:47 ` Jeff King
2008-06-12 10:21 ` Johan Herland
2008-06-12 12:20 ` Stephen R. van den Berg
2008-06-10 19:40 ` Recovering from repository corruption Nicolas Pitre
2008-06-10 19:42 ` Denis Bueno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200806102214.40805.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=dbueno@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).