Johan Ung Posted June 30, 2017 Report Share Posted June 30, 2017 Hi, ran into a problem when trying to migrate a SVN repository to Plastic (going via Git). I'm using SCM-Manager (v 1.54) to host Git the git repository, no errors in console output there. I get an Assertion failed according to the attached image. Attached error from windows event viewer and server logs as well. Any suggestions of things I should try? Plastic SCM version 6.0.16.1271 Best Regards, Johan plastic.debug.log.txt plastic.relevant.log.txt plastic.channelcall.log.txt win-event-error.txt Link to comment Share on other sites More sharing options...
Johan Ung Posted June 30, 2017 Author Report Share Posted June 30, 2017 Tried it again and it took longer for it to fail, this time no assertion but an error saying "The operation has timed out". I get "Receiving references... OK", percentage increases and then error. Link to comment Share on other sites More sharing options...
manu Posted June 30, 2017 Report Share Posted June 30, 2017 Hello Johan, it seems the git library we use (git2x64.DLL) is failing Do you need to keep the two repositories in sync? If it's just a migration I think in your case you can try the fast-export/import way: http://blog.plasticscm.com/2011/10/connecting-plastic-scm-to-github.html Link to comment Share on other sites More sharing options...
Johan Ung Posted July 3, 2017 Author Report Share Posted July 3, 2017 Hi manu, I actually tried the fast-export way first but had some issues with filenames containing none-ascii characters (åäö). Found some old posts about similar issues on the forum but didn't find any way of working around it. I guess renaming the files won't help since they still have a bad name in history? Link to comment Share on other sites More sharing options...
Johan Ung Posted July 13, 2017 Author Report Share Posted July 13, 2017 Found a way to get fast-export/import working (convert octal utf8 to hex in fast-export:ed file), thanks. Link to comment Share on other sites More sharing options...
calbzam Posted July 14, 2017 Report Share Posted July 14, 2017 Thanks for the update! Link to comment Share on other sites More sharing options...
Johan Ung Posted July 14, 2017 Author Report Share Posted July 14, 2017 Gah.. next problem =) After processing 180 changesets I get an error (according to attached file). Any ideas? My fast-export:ed file is ~427GB so I haven't been able to open it yet and try to see if anything looks suspicious. BR, Johan fast-import-error.txt Link to comment Share on other sites More sharing options...
Johan Ung Posted July 17, 2017 Author Report Share Posted July 17, 2017 Tried to remove the failing file/commit from history (in Git using BFG), still get an error in Plastic fast import after 180 processed changesets. Link to comment Share on other sites More sharing options...
manu Posted July 18, 2017 Report Share Posted July 18, 2017 Same error as before? If you create for us a git no-data fast-export file we can check if we can find the error. Link to comment Share on other sites More sharing options...
Johan Ung Posted July 19, 2017 Author Report Share Posted July 19, 2017 Yup same error. I revisited the GitSync option and tried to get that working instead, cloning a bare repo and trying to avoid delta packing I was able to get another error (attached image). Now it's time to confess, I missed a very obvious thing that at least caused this last error. Out of disk. So, freeing up some disk space and running GitSync again I'm all the way to 99% when it fails due to "An existing connection was forcibly closed by the remote host", so I guess that git-daemon closed the socket. I'm trying yet again with ScmManager as the Git sever instead, bare repo and enough free disk space. Fingers crossed. Looks like the temp file that fills up disk space is created by the git lib you use, files are created similar to this location: C:\Users\johan.ung\AppData\Local\Temp\c5453f4d-3c0f-4528-bc64-ac19c3629af8\pack_git2_a13552. Maybe something to investigate if the size of this temp file could be reduced during GitSync in the future. (If this fails again I'll try to get you a no-data export file as well) BR, Johan Link to comment Share on other sites More sharing options...
manu Posted July 19, 2017 Report Share Posted July 19, 2017 Thanks for all the info, keep us posted with the last attempt result. Link to comment Share on other sites More sharing options...
Johan Ung Posted July 20, 2017 Author Report Share Posted July 20, 2017 Unfortunately yet another error message, see attachement. Link to comment Share on other sites More sharing options...
Johan Ung Posted July 20, 2017 Author Report Share Posted July 20, 2017 Tried another repo and got this error Edit: Hmm, never mind, got an error on the Git server side that probably was the root cause. Link to comment Share on other sites More sharing options...
manu Posted July 20, 2017 Report Share Posted July 20, 2017 Is there a way for you to fast-export the repositories without data and send it to us? We'll try to debug it. The libgit2 library error is scary and will be harder to fix. Link to comment Share on other sites More sharing options...
Johan Ung Posted July 21, 2017 Author Report Share Posted July 21, 2017 I'll send you a PM with link to the fast export dump manu. Link to comment Share on other sites More sharing options...
manu Posted July 25, 2017 Report Share Posted July 25, 2017 Got it! Answered via PM Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.