Closed ebadedude closed 12 years ago
Not sure how, but this seemed to be a memory issue for me. Also, interesting to note that the command svn2git seems to pick up from where it left off the last time it was run. so if you cannot perform a capacity/memory upgrade (assuming you run into interesting errors), just run the svn2git command again.
I ran into the same problem with a huge svn repository, the git command got killed by the oomkiller:
Can't fork at /usr/share/perl5/vendor_perl/Git.pm line 1260.
-- dmesg: Out of memory: Kill process 20606 (git-svn) score 573 or sacrifice child Killed process 20606, UID 1003, (git-svn) total-vm:5586360kB, anon-rss:4799832kB, file-rss:28kB
Reran the git svn fetch command and the process resumed.
Unfortunately this looks like a problem in git-svn, which is part of the official git offering. svn2git is a nicer wrapper to git-svn. Any bugs found in Perl should be reported to the git developers list or their issue tracker.
I am not sure if this is an issue with svn2git or something else. when I run the following command:
It seems to run fine and at about 30 minutes into the process, I get the following
Looking at the file Git.pm, I am not sure what should happen:
I was hoping someone ran into this issue as well and what they did to resolve it.