problem pushing large changeset to remote repo.

[Matt Mackall]

On Tue, 2008-01-22 at 11:12 -0800, Dave Peck wrote:
> My "personal projects" code base consists of 7,287 files that consume 438MB
> of disk (before being added to a local repo.) I've decided to move this code
> from my old SCM to Mercurial.
> 
> I had no trouble adding these files to a local HG repository. But I also
> maintain a remote machine where I'd like to back them up to. 
> 
> As I expected, pushing my initial 7,287-file change to the remote machine
> took quite some time. But something went wrong in the process; see the last
> line of output:
> 
>   dave at localMachine$ hg -v push ssh://hg@remotemachine.org/repos/personal 
>   running ssh hg at remotemachine.org "hg -R repos/personal serve --stdio"
>   Password:
>   pushing to ssh://hg@remotemachine.org/repos/personal
>   searching for changes
>   2 changesets found
>   remote: adding changesets
>   remote: adding manifests
>   remote: adding file changes
>   remote: added 2 changesets with 7287 changes to 7287 files
>   remote: abort: No such file or directory: /tmp/hg-unbundle-66MEJz
> 
> Did I just run out of tmp space? What state is my remote repo in?

<psychic powers>
California?
</psychic powers>

Looks like the changesets were added just fine. But for some mysterious
reason, the bundle file disappeared in the middle of that. That may have
triggered a rollback, in which case your repo is now empty again.

My suspicion is you're running this on a system like Dreamhost, which
apparently has nasty little programs that kill /tmp files and processes
that use much CPU.

> In general, is HG capable of efficiently handling changes to repos of this
> size? I had about 3,700 commits in my old SCM system.

Absolutely. There are repos with >100k file and >100k commits. You will
get into trouble if you commit extremely large files though. The
practical limit for a single file is within an order of magnitude of
100MB.

-- 
Mathematics is the supreme nostalgia of our time.