git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Abrahams <dave@boostpro.com>
To: Thomas Ferris Nicolaisen <tfnico@gmail.com>
Cc: Andres Freund <andres@anarazel.de>,
	Jonathan Nieder <jrnieder@gmail.com>,
	git@vger.kernel.org
Subject: Re: git-svn dying unceremoniously
Date: Wed, 13 Apr 2011 10:27:55 -0400	[thread overview]
Message-ID: <BANLkTincypeToMmKWYZmp26Y-3wP6bt5Yw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinnRwas8VSn4p+NRvrwxnVSwBRc1Q@mail.gmail.com>

On Wed, Apr 13, 2011 at 8:46 AM, Thomas Ferris Nicolaisen
<tfnico@gmail.com> wrote:
> On Tue, Apr 12, 2011 at 6:02 PM, Dave Abrahams <dave@boostpro.com> wrote:
>> I managed to get a lot farther with
>>
>>   while ! git svn fetch ; do sleep 1 ; done
>>
>> But eventually I exceeded my disk quota:
>>
>> error: bad index file sha1 signature
>> fatal: index file corrupt
>> write-tree: command returned error: 128
>>
>
> I've run into this in my git-svn clones as well. It happened once last
> year. I tried this trick I found googling around:
>
> rm -f .git/index
> git read-tree --reset HEAD
> git status
>
> .. but it didn't help. I ended up re-doing the git svn clone. Since
> then it has worked fine.

Yeah, I'm redoing mine as well.  It'll probably "only" take another 24
hours to finish, but at least it doesn't seem to be getting stuck!

Thanks, all

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com

      reply	other threads:[~2011-04-13 14:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11 22:00 git-svn dying unceremoniously Dave Abrahams
2011-04-12  2:12 ` Jonathan Nieder
2011-04-12  6:50   ` Andres Freund
2011-04-12 16:02     ` Dave Abrahams
2011-04-13 12:46       ` Thomas Ferris Nicolaisen
2011-04-13 14:27         ` Dave Abrahams [this message]

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=BANLkTincypeToMmKWYZmp26Y-3wP6bt5Yw@mail.gmail.com \
    --to=dave@boostpro.com \
    --cc=andres@anarazel.de \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=tfnico@gmail.com \
    /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).