> We regularly have working copies in the 25k file/500MB range, and
> have never had problems. Other people have much larger repositories.
> I don't think your issue is related to any inherent scaling issue
> in Subversion.
That's fantastic news, because it means that any problems are my fault
and I can resolve them. I'm definitely relieved to read that.
> How do they fail? What is the error message? Does it always fail at
> point, on the same file?
with tortoise, the transfer just started slowing down more and more and
more until it ground to a halt. With the command line version, it
checked out quite a lot of data, and then finally aborted. I neglected
to save the message though.
> Unless it crashed hard I don't think it should ever leave the working
> copy in a broken state. But then unless you're using 1.4.2 client
> it is a bug that's already been fixed.
> What OS versions on server and client?
> What version of svn are you running on the server and client? Did you
> yourself or are they the stock/distro binaries?
> What server type (svnserve or apache)? What backend (fsfs or bdb)?
client 1.4.2 (r22196), prebuilt binary.
server 1.4.2 (r22196), prebuilt binary.
server linux, 2.6.18 kernel, fedora core 6 distro.
client windows xp.
backend was fsfs
alfonso e. urdaneta
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
This e-mail and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom
they are addressed.
If you have received this e-mail in error please notify the
originator of the message. This footer also confirms that this
e-mail message has been scanned for the presence of computer viruses.
Any views expressed in this message are those of the individual
sender, except where the sender specifies and with authority,
states them to be the views of Indra Systems, Inc.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Nov 29 17:00:01 2006