From: Alexander Litvinov <litvinov2004@gmail.com>
To: git@vger.kernel.org
Subject: My git repo is broken, how to fix it ?
Date: Wed, 28 Feb 2007 10:36:30 +0600 [thread overview]
Message-ID: <200702281036.30539.litvinov2004@gmail.com> (raw)
Hello,
I use manualy compiled git under cygwin. Some time ago I have imported project
from CVS and start to us it under git. To emulate 'separate remotes' schema
for branches from CVS I clone imported git repo and work with it. From time
to time I incrementaly update imported repo from cvs and sometimes use
git-cvsexportcommit (from work repo) to export my changes and then get them
using git-cvsimport.
Some times ago I descide to run fsck and found that by working repo is broken,
while imported repo is correct. Is there way to fix it ?
>git version
git version 1.5.0.GIT
(It was actualy compiled from e86d552 commit)
> git fsck
> git fsck --full
error: packed 7f5fed8131fb32972c602dede29b9257a053ba67
from .git/objects/pack/pack-c4554978bbe079c9a43d6a13546a2fa314fe0884.pack is
corrupt
sha1 mismatch 7f5fed8131fb32972c602dede29b9257a053ba67
(This is a blob, git cat-file blob 7f5fed813 shows me my c++ header file that
is partialy broken with ^@ symbols)
The repo I get using git-cvsimport is correct and does not contains that blob.
I also tried git-log -p for all by branches to force git to show me what is
the commit was broken but git-log finished without errors.
By the way, several times I interrupt git's commands like commit and pull
using Ctrl-C.
I tried to unpack all objects:
> git-unpack-objects -r
< .git/objects/pack/pack-c4554978bbe079c9a43d6a13546a2fa314fe0884.pack; echo
$?
Unpacking 12868 objects
100% (12868/12868) done
0
No erorts here. But fsck find that broken blob:
> git fsck
dangling blob beb992198d4d8813ea51fd1cbbf38313ef490c22
git-cat-file shows me this this is a broken object with correct sha1 sum.
As a cunclusion: my repo has broken file and I don't see there is the brakage.
Can I reconstruct file by sha1 sum :-) or can I do something to stop fsck
warn me ?
next reply other threads:[~2007-02-28 4:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 4:36 Alexander Litvinov [this message]
2007-02-28 4:57 ` My git repo is broken, how to fix it ? Linus Torvalds
2007-02-28 11:54 ` Alexander Litvinov
2007-02-28 16:19 ` Linus Torvalds
2007-02-28 19:12 ` Alex Riesen
2007-03-19 13:32 ` Alexander Litvinov
2007-03-19 15:20 ` Linus Torvalds
[not found] ` <200703201013.39169.litvinov2004@gmail.com>
2007-03-20 5:34 ` Linus Torvalds
2007-03-20 6:55 ` Alexander Litvinov
2007-03-20 7:42 ` Junio C Hamano
2007-03-20 15:23 ` Nicolas Pitre
[not found] ` <Pine.LNX.4.64.0703200832150.6730@woody.linux-foundation.org>
[not found] ` <Pine.LNX.4.64.0703200836490.6730@woody.linux-foundation.org>
[not found] ` <200703210956.50018.litvinov2004@gmail.com>
2007-03-22 15:58 ` Linus Torvalds
2007-03-22 16:34 ` Nicolas Pitre
[not found] ` <200703211024.04740.litvinov2004@gmail.com>
2007-03-22 16:17 ` Linus Torvalds
2007-03-22 16:29 ` Linus Torvalds
2007-03-22 16:48 ` Linus Torvalds
2007-03-22 17:01 ` Nicolas Pitre
2007-03-22 17:10 ` Linus Torvalds
2007-03-22 17:28 ` Nicolas Pitre
2007-03-22 22:13 ` Jeff King
2007-03-23 0:25 ` Linus Torvalds
2007-03-23 0:42 ` Bill Lear
2007-03-23 0:51 ` Jeff King
2007-03-22 20:31 ` [PATCH] git-apply: Do not free the wrong buffer when we convert the data for writeout Junio C Hamano
2007-03-22 20:55 ` Linus Torvalds
2007-03-23 3:55 ` Alexander Litvinov
2007-03-23 3:40 ` My git repo is broken, how to fix it ? Alexander Litvinov
2007-03-22 17:12 ` Johannes Sixt
-- strict thread matches above, loose matches on Subject: below --
2021-06-06 17:27 B
2021-06-06 17:28 B
2021-12-25 8:30 Joseph Mitchell
2021-12-26 0:48 ` Lemuria
2023-05-29 18:57 ross thomas
2024-09-17 4:13 Hope Hovenga
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=200702281036.30539.litvinov2004@gmail.com \
--to=litvinov2004@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.