Re: Git import of cvs2git dumpfile

Michael Haggerty <[email protected]> Mon, 12 Aug 2013 16:03:17 +0200
Newsgroups gmane.comp.version-control.subversion.cvs2svn.user
Message-ID <[email protected]>
On 08/12/2013 03:28 PM, Fabian Schäfer wrote:
>>What command did you use to load the files?  Did it crash when loading
>>the blob file or the dump file or did you load them both at the same
>>time?  If you were loading them at the same time, you might try loading
>>them separately:
>>
>>    git fast-import --export-marks=FILENAME <git-blob.dat
>>    git fast-import --import-marks=FILENAME <git-dump.dat
>>
>>and see which of the processes dies.
> 
> I tried both. And the blob-file import does work very well. It
> interrupts when I try to import the dump file.
> 
>>Did you monitor the size of the "git fast-import" process before it
>>died?  Was it slowly eating up the available 72 Gb?
> 
> Yes, I have monitored the consumption. the process uses less than 10% of
> memory. So a swapfile is never used.

If the process runs out of memory after using only 7 GB on a machine
with 72 GB of RAM + swap, then it sounds very much like something else
is limiting the process's memory consumption.  Perhaps ulimits or quotas
or ...  Can you get *any* process to allocate more memory when run the
same way that you ran git-fast-import?

Are other processes running on the computer at the same time?  Maybe
something else is eating up 65 Gb.

I very much hope that the computer is running in 64-bit mode, and that
git-fast-import was compiled for 64-bits.  Otherwise you could run out
of virtual address space after only 4 GB.

It is hard to imagine how this could be a git-fast-import bug, let alone
a cvs2git bug.

If you give me a computer with 32 GB of RAM I'd be happy to do some
testing :-)

Michael

-- 
Michael Haggerty
[email protected]
http://softwareswirl.blogspot.com/

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=3062473

To unsubscribe from this discussion, e-mail: [[email protected]].