Hi,
I wrote:
> I'm having similar problems myself.
> [...]
> So I've tried running p42svn.pl directly on the Perforce server, but it
> ran out of memory and I had to reboot the server. I have aksed sysadmins
> to buy RAM or the server (128 Mb -> 512 Mb).
This server has now been upgraded to 640 MB of RAM. Unfortunately it
looks like this is still not enough, p42svn.pl currently fails while
converting a 1,9 GB Perforce depot. I'll try to add 512 MB of additional
RAM and see if it helps.
This could be a memory leak in the P4 Perl module, it looks like memory
usage grows linearly with time.
Anyway, there are indeed many problems with p42svn.pl, hopefully
throwing lots of RAM into the server will help in most cases. I just
hope I won't have to upgrade to a 64-bit server with more than 2 GB of
RAM to convert our Perforce depot to a Subversion dump file.
> [...]
> By the way I got an error message while running the latest p42svn.pl:
> Not an ARRAY reference at /home/user/p42svn.pl line 639.
> which I got rid of by commenting out line 639 and I also got warnings:
> Key (depotFile) not a reference! at P4.pm line 211.
> Key (rev) not a reference! at P4.pm line 211.
> which I ignored.
This is a known problem with the current stable release of P4 (3.4804).
This problem is fixed in recent development versions. Unfortunately the
current development versions (3.5073) suffer other serious problems so I
had to revert to 3.4804 and ignore these messages:
http://maillist.perforce.com/pipermail/p4perl/2005q4/000133.html
Dimitri Papadopoulos
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 14 13:59:37 2005