From: Christian Couder <christian.couder@gmail.com>
To: Sylvestre Ledru <sylvestre.ledru@scilab.org>
Cc: git@vger.kernel.org, Simon Gareste <simon.gareste@scilab.org>,
Bruno JOFRET <bruno.jofret@scilab.org>
Subject: Re: Corruption in the repository
Date: Mon, 13 Dec 2010 18:02:06 +0100 [thread overview]
Message-ID: <AANLkTimgLhQMUGmC=W5wpcAvb07faw4HOzPgWXpFA4u1@mail.gmail.com> (raw)
In-Reply-To: <1292258845.25237.27680.camel@korcula.inria.fr>
On Mon, Dec 13, 2010 at 5:47 PM, Sylvestre Ledru
<sylvestre.ledru@scilab.org> wrote:
>
> Le lundi 13 décembre 2010 à 17:34 +0100, Christian Couder a écrit :
>> Hi,
>>
>> On Mon, Dec 13, 2010 at 4:59 PM, Sylvestre Ledru
>> <sylvestre.ledru@scilab.org> wrote:
>> > Hello guys,
>> >
>> > I have a small problem with a git repository and I haven't find a way to
>> > fix my problem.
>> > I am using git with gerrit [1] as frontend (even if I don't think it is
>> > related here).
>> > For an unknown reason, the repository just became corrupted.
>> >
>> > When I try to clone the repository straight with the file system, the
>> > following error is displayed:
>> > error: refs/changes/98/398/1 does not point to a valid object!
>> > error: refs/changes/98/398/2 does not point to a valid object!
>> > fatal: object cff52c24fba28408e7d021a8f35a717bef31521d is corrupted
>> > fatal: The remote end hung up unexpectedly
>> >
>> > git-prune & git-fsck both fail.
>> >
>> > Does anyone know how to repair this error ?
>>
>> Did you try what the FAQ suggests:
>>
>> https://git.wiki.kernel.org/index.php/GitFaq#How_to_fix_a_broken_repository.3F
> Yes. It shows an other error and it doesn't match the error described on
> this URL [1].
>
> I get the following:
> error: refs/tags/5.3.0-beta-4 does not point to a valid object!
> fatal: object 555a7c359b2e589ec10822d9b56cdfeee0105fe0 is corrupted
The FAQ says that you should try to replace any broken and/or missing
objects, so you should try to do that with object
555a7c359b2e589ec10822d9b56cdfeee0105fe0 (as described in the FAQ)
even if the error message is not exactly the same.
Regards,
Christian.
next prev parent reply other threads:[~2010-12-13 17:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 15:59 Corruption in the repository Sylvestre Ledru
2010-12-13 16:34 ` Christian Couder
2010-12-13 16:47 ` Sylvestre Ledru
2010-12-13 17:02 ` Christian Couder [this message]
2010-12-13 18:11 ` Sylvestre Ledru
2010-12-14 9:29 ` Christian Couder
2010-12-14 9:46 ` Jonathan Nieder
2010-12-14 9:59 ` Sylvestre Ledru
2010-12-14 9:47 ` Sylvestre Ledru
2010-12-14 11:59 ` Christian Couder
2010-12-14 14:37 ` Sylvestre Ledru
2010-12-14 19:19 ` Jonathan Nieder
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='AANLkTimgLhQMUGmC=W5wpcAvb07faw4HOzPgWXpFA4u1@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=bruno.jofret@scilab.org \
--cc=git@vger.kernel.org \
--cc=simon.gareste@scilab.org \
--cc=sylvestre.ledru@scilab.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).