Incomplete data: Delta source ended unexpectedly while git svn fetch

I have cloned my svn repo into git and everyday i am doing git svn fetch (i only do changes in SVN) but i am planning to move to git and i keep the git repo in sync for the day since the svn clone tooke me 2 weeks (yeah it’s a big repo).

Anyway the git svn fetch has worked fine every day until 2 days ago where i now get

  • Cannot add to github: Gist does not support directories
  • How to tell which git branch is checked out?
  • “modified: Gemfile.lock”, Why?
  • Pod from github not working
  • Why doesn't “git branch” show anything in my new BitBucket clone?
  • Git URL Structure
  • Incomplete data: Delta source ended unexpectedly at /usr/lib/perl5/site_perl/Git/SVN/ line 290

    at a specific revision. I tried the different suggestions online about git svn reset and going back some revisions and i went about 20 revisions back with no luck. I also tried to run :

    git config --get core.autocrlf

    which gave true.

    I know that the svn repo is working good, i have no issues doing svn up.

    Any ideas how i can get back on track to sync again ? I am stuck without ideas what to try.

    I might reveal one issue. I don’t recall but before running the issue i might have had a disk full on the disk where the repo is when i tried the fetch. Maybe that destroyed something ?


  • Can golang import package from private subversion repository?
  • Git rebase hits “Out of memory, malloc failed” error
  • cvs2git: Possibility to keep mapping from CVS revision numbers to Git revision Hash
  • How do I keep my local version of files, without using .gitignore?
  • How to do a git pull with an in-memory database in JGit?
  • git clone can't resolve proxy
  • One Solution collect form web for “Incomplete data: Delta source ended unexpectedly while git svn fetch”

    1. Make sure there are no additional git/perl processes running (which could create the index.lock file and mess up the current fetch). Kill’em all.
    2. Delete the …\my_repository.git\.git\svn\refs\remotes\trunk\index.lock file
    3. git svn reset -r SomeSVNRevisionNumberBeforeTheProblematicOne
    4. git svn fetch

    Fetch should continue from the SomeSVNRevisionNumberBeforeTheProblematicOne.

    The most probable reason why this happened is concurrency between two git instances running simultaneously on the same repository.

    Git Baby is a git and github fan, let's start git clone.