Cloning Question

Josh Malinski JMalinski at anasazisoftware.com
Thu Jan 7 14:49:03 CST 2010


Oops forgot to answer the second part, we are using 1.4.1.

--Josh


-----Original Message-----
From: Matt Mackall [mailto:mpm at selenic.com] 
Sent: Thursday, January 07, 2010 11:40 AM
To: Josh Malinski
Cc: mercurial at selenic.com
Subject: Re: Cloning Question

On Thu, 2010-01-07 at 10:35 -0700, Josh Malinski wrote:
> Greetings,
> 
>  
> 
> I have been using Mercurial for some time now on local projects and
> have had good success however now I am running into an issue trying to
> implement it on a greater scale. I have a binary file that is over
> 100Mb in size (I know I shouldn’t be tracking this size of a file but
> I am). When I clone the repository on another machine to its local
> disk everything runs just fine, however when I try to clone the
> repository to a disk that is stored on our filer the clone fails
> without any log message that I can find but when it fails it is on
> this 100Mb file. I am pretty sure that the problem isn’t with
> Mercurial and the problem is with our filer but I need to have some
> sort of trail so that I can push back at our vendor. So with that
> being said is there a log or a mode of some sort that I can run the
> clone in to generate a log of some sort.

How much memory do you have on the server? Which version of Mercurial
are you using? If you've got a 100MB file, recent Mercurial's memory
needs may be on the order of 600MB.

If your server is administered by a third party, they may also have
process memory limits that come into effect.

-- 
http://selenic.com : development and support for Mercurial and Linux




More information about the Mercurial mailing list