I've been using TortoiseSVN for a few weeks now, and all has been
working well. However, it's recently started giving me problems -
originlly when committing, and now updating, largish files.
I've been accessing the repository with an svn+ssh:// protocol so far -
I have putty installed, with the key held within pageant. The URL is of
the form svn+ssh://user@machine/path/to/repos and I'm using tortoiseplink.
The main symptom is when I go to commit a largish file (say 4MB). When
the commit process gets to the file, the client machine hits 100% load
(in tortoiseplink), while the server remains untroubled (although a
process list shows that the SSH connection has been made. The file is
never transferred, and the whole process just freezes. I've left it for
up to 2 hours, but its definitely stuck. It ignores the "cancel button",
but does stop if I hit the X button top-right.
Note that when things were working, I've dealt with much larger files -
certainly up to 75MB.
When I copied the file over to a Linux machine and committed it there, I
found that I then couldn't perform an update back on the Windows box
using TortoiseSVN - exactly the same symptoms. Same result if I try a
I then temporarily made the repository available through svnserve
directly, and tried a new checkout using the svn:// protocol - this
worked just fine (I can't commit back because I haven't set up
The problem isn't a particular file - I have quite a few now that won't
commit. And it does seem to be size - I can still commit small files in
other directories (same repository).
And of course, my linux client can perform commits & updates without
fault, all using the svn+ssh:// protocol.
Windows XP SP2.
Linux Fedora Core 5
I have tried the recent 1.4 RC too, which also exhibits the same problem
on the checkout side at least. I don't want to try on my real working
copy though - not just yet.
I'm now at something of a loss as to how to investigate further. I'm
getting no errors, and no logs, on either the client or the server. Just
files that won't behave, and a machine that just jumps to 100%.
Can anyone offer some suggestions?
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Aug 22 03:11:29 2006