From: gitml.jexpert@recursor.net
To: git@vger.kernel.org
Subject: Reproducible, corrupt packfile after fresh
Date: Thu, 08 Aug 2013 13:56:30 +0200 [thread overview]
Message-ID: <f1d8f80d6fa3678ac043bfdb19bebf6bf4261273@localhost> (raw)
In-Reply-To: <52037F84.9060006@exxcellent.de>
I'm a heavy user of git-svn and experience an issue with one specific
(git-svn) repository: 'git fsck' reports a corrupt packfile after every
checkout.
Now I'm totally puzzled about the cause and what do about it.
This is what I do:
git svn init -s http://svn.foo.com/myproject myproject.git
cd myproject.git
git svn fetch # Much more reliable than 'git-svn clone'
This checks out ~2100 commits and executes 2 git-gc during checkout. The
final .git repo size is about 940MB. Then I run
git fsck
➜ myproject.git git:(master) git fsck
Checking object directories: 100% (256/256), done.
error: packed 0f5f33639bfc1a781fe080c31a1f076d9a25c1d3 from
.git/objects/pack/pack-6a6f5355584a5d71215d5fc867ce09602ceab533.pack is
corrupt
*** glibc detected *** git: free(): invalid pointer: 0x00007f46a09e9010 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7f46d9ebab96]
git[0x4ddf46]
git[0x4b4123]
git[0x431524]
git[0x405ce8]
git[0x4050e2]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f46d9e5d76d]
git[0x405529]
======= Memory map: ========
00400000-0055f000 r-xp 00000000 fc:01 12452043
/usr/bin/git
0075e000-0075f000 r--p 0015e000 fc:01 12452043
/usr/bin/git
....
This only affects this very particular git-svn repo (and I have dozens
of them). The error happens reproducible on every fresh checkout as
described above. The backtrace does not appear always. The object is a
very large blob
git show 0f5f33639bfc1a781fe080c31a1f076d9a25c1d3 | wc -c
39524691
Any hints what to do?
Thanks
- Ben
next parent reply other threads:[~2013-08-08 11:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52037F47.5010302@exxcellent.de>
[not found] ` <52037F84.9060006@exxcellent.de>
2013-08-08 11:56 ` gitml.jexpert [this message]
2013-08-08 12:13 ` Reproducible, corrupt packfile after fresh Thomas Rast
2013-08-08 12:23 ` Reproducible, corrupt packfile after fresh git-svn checkout gitml.jexpert
2013-08-08 12:31 ` Thomas Rast
2013-08-08 13:12 ` Reproducible, corrupt packfile after fresh git-svn checkout message 3 of 20) gitml.jexpert
2013-08-08 13:18 ` Matthieu Moy
2013-08-08 13:27 ` Reproducible, corrupt packfile after fresh git-svn checkout message gitml.jexpert
2013-08-08 13:34 ` Matthieu Moy
2013-08-08 13:43 ` Reproducible, corrupt packfile after fresh git-svn checkout message (gitml: message 5 of 20) gitml.jexpert
2013-08-08 14:20 ` Thomas Rast
2013-08-08 14:53 ` Reproducible, corrupt packfile after fresh git-svn checkout message (gitml: message 5 of 20) (gitml: message 6 " Ben Tebulin
2013-08-08 15:28 ` Thomas Rast
2013-08-08 16:36 ` Reproducible, corrupt packfile after fresh git-svn checkout message Ben Tebulin
2013-08-08 16:48 ` Matthieu Moy
2013-08-08 17:38 ` Reproducible, corrupt packfile after fresh git-svn checkout message (gitml: message 5 of 20) (gitml: message 6 of 20) Junio C Hamano
2013-08-09 12:27 ` Reproducible, corrupt packfile after fresh git-svn checkout message Ben Tebulin
2013-08-09 12:54 ` Stefan Beller
2013-08-14 9:29 ` Reproducible, corrupt packfile after fresh git-svn checkouts - IDENTIFIED Ben Tebulin
2013-08-14 9:09 ` Reproducible, corrupt packfile after fresh git-svn checkout message Thomas Rast
2013-08-14 9:47 ` Ben Tebulin
2013-08-15 9:32 ` Ben Tebulin
2013-08-15 14:46 ` Junio C Hamano
2013-08-08 13:20 ` Reproducible, corrupt packfile after fresh git-svn checkout message 3 of 20) Thomas Rast
2013-08-08 12:38 ` Reproducible, corrupt packfile after fresh git-svn checkout Matthieu Moy
2013-08-08 12:41 ` Stefan Beller
2013-08-08 12:18 ` Reproducible, corrupt packfile after fresh Stefan Beller
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=f1d8f80d6fa3678ac043bfdb19bebf6bf4261273@localhost \
--to=gitml.jexpert@recursor.net \
--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).