TortoiseHG - Large File Commit (only 40Meg is size)

Adrian Buehlmann adrian at cadifra.com
Sat Jan 1 04:38:01 CST 2011


On 2011-01-01 10:46, mutface wrote:
> 
> Hi Mads, 
> 
> I'm using TortoiseHg as my client and I do not type a single command.
> Everything is done through TortoiseHg. TortoiseHg has a GUI and all commits,
> push, etc are effected through it. 

Yes. I think we got that by now. But most Mercurial developers don't
know much about the TortoiseHg GUI and if they ask you to try something
on the command line, then please do so. Using the command line hg
command makes sure that the smallest possible amount of software is
used, which helps to nail down problems.

As you demonstrate below, the traceback can be produced with the hg
command line command alone.

> Anyways, I just tried using command prompt and here is what I got:-
> 
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
> 
> s:\xyz\>hg commit --traceback -m "upload maps"
> trouble committing content/maps/kwai_chung1.psd!
> transaction abort!
> rollback completed
> Traceback (most recent call last):
>   File "mercurial\dispatch.pyo", line 58, in _runcatch
>   File "mercurial\dispatch.pyo", line 590, in _dispatch
>   File "mercurial\dispatch.pyo", line 401, in runcommand
>   File "mercurial\dispatch.pyo", line 641, in _runcommand
>   File "mercurial\dispatch.pyo", line 595, in checkargs
>   File "mercurial\dispatch.pyo", line 588, in <lambda>
>   File "mercurial\util.pyo", line 427, in check
>   File "mercurial\commands.pyo", line 780, in commit
>   File "mercurial\cmdutil.pyo", line 1333, in commit
>   File "mercurial\commands.pyo", line 775, in commitfunc
>   File "mercurial\localrepo.pyo", line 962, in commit
>   File "mercurial\localrepo.pyo", line 1009, in commitctx
>   File "mercurial\localrepo.pyo", line 781, in _filecommit
>   File "mercurial\context.pyo", line 906, in data
>   File "mercurial\localrepo.pyo", line 615, in wread
> IOError: [Errno 22] Invalid argument
> abort: Invalid argument

(note: I assume this is still with Mercurial-1.7.2 on Windows XP 32-bit
with 1.5 Gb of RAM, as mutface noted in their initial post).

mutface: perhaps you can tell us a bit more about your drive s:?

Is s: a local drive? If yes, what file system is it using? NTFS? On what
hardware is that? Harddisk? Have you installed any special device drivers?

Or is s: a Windows share? If yes, what software is s: serving? Windows
or Samba? What versions exactly?

Are you using any on-access antivirus scanners? If yes what's the
product name?


More information about the Mercurial mailing list