push error: remote: abort: No such file or directory: /tmp/hg-unbundle-e4YkMW

[Chris Peterson]

I was able to create the bundle.hg on my local machine, though it took about
4 hours and the hg process used over 1 GB of virtual memory at times.

I was unable to "hg pull bundle.hg" on the Linux server because the hg
process was killed. Apparently the server (running at DreamHost) has a
procwatch policy to kill processes using more than 500 MB of virtual memory.

I've read that git has the same problem on DreamHost servers, but some users
avoid the memory limit by recompiling git with NO_MMAP=1 to reduce the
virtual memory footprint.

chris


On Sun, May 4, 2008 at 12:23 PM, Adrian Buehlmann <adrian at cadifra.com>
wrote:

> On 04.05.2008 20:18, Chris Peterson wrote:
> > I have a small hg repo hosted on a remote Linux server (that I do not
> > admin). I added some big binary files to my local repo clone: 2 GBs of
> > files, some 10+ MB. The local commit succeeded, but when I try to push
> > the changeset to my remote repo (using ssh) I get the following error
> > message:
> >
> > remote: abort: No such file or directory: /tmp/hg-unbundle-e4YkMW
>
> It seems that temp file could get very large in your case.
>
> How much free disk space is available on /tmp on that remote server?
>
> Instead of direct pushing over the net, you could create a bundle file
> locally
> (see hg help bundle) and transfer that manually to the server
> side and then use hg pull from that bundle there (see hg help pull):
>
> On local:
>  $ cd local-repo-dir
>  $ hg bundle bundle.hg remote-repo-url
>
> creates local file bundle.hg that contains the changesets that
> are missing in the remote repo. Then on remote do:
>
>  $ cd remote-repo-dir
>  $ hg pull bundle.hg
>
> The bundle file is compressed, so this is very efficient.
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20080505/4e8b4309/attachment.htm