git-svn dying unceremoniously

Does anyone know a cure for this?

% git svn fetch

        A       boost/boost/graph/uniform_cost_search.hpp
        A       boost/boost/graph/properties.hpp
        A       boost/boost/graph/smallest_last_vertex_ordering.hpp
        A       boost/boost/graph/johnson_all_pairs_shortest_paths.hpp
        .
        .
        .
        A       boost/libs/graph/docs/MutableGraph.html

r7701 = c2434d3062416adac72b370ce3b993a9857e2029 (refs/remotes/trunk)
error: git-svn died of signal 13

See
http://thread.gmane.org/gmane.comp.version-control.git/134936/focus=134940
and the surrounding thread for hints.

Hi,

Quoted 3 lines · On Tuesday 12 April 2011 04:12:24 Jonathan Nieder wrote:

See
http://thread.gmane.org/gmane.comp.version-control.git/134936/focus=134940
and the surrounding thread for hints.

I hit that again some days ago and after stracing I started dumping the network transfer. For me it looks like the server simply closes the connection. Seemingly always directly after a tls key renegotiation... I didn't dig further so far.

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

Quoted 10 lines · Dave Abrahams

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.