Hi,
I'm using svn 0.29 on win32, and am experiencing problems with long
commits. My repository is on a local disk, accessed through ra_local
(file:// url) and is not being used by anyone else (private).
There are two problems, but I believe the first is already a known bug.
I have a very large repository (7Gb, 270k files, 25k folders), and
running a commit (or a number of other commands) in any directory near
the top of the repository takes an extremely long time to complete, even
when -N is given. I believe this is the known issue with locks being
taken out on all child dirs.
However, this triggers another issue; once a commit has taken a certain
length of time to run (seems to be a few mins but I've not tested
thouroughly), the commit will usually fail. The exact command/response
(executing a commit from the root of the working copy):
F:\nt>svn commit -Nm"Update ignores"
Sending .
svn: Transaction is out of date
svn: Commit failed(details follow):
svn: out of date: `/nt' in txn `39'
svn up and svn update -u both show the working copy as up to date.
For this example it took over 10 minutes to get as far as printing
'sending', and another few minutes after that before the error. The only
change that this command should be committing is a change to a property
set on the current directory.
This happens almost every time I try to commit on any directory near the
top of my working copy. I'm pretty sure this is a bug; I've been on #svn
on freenode and nobody there had any suggestions other than what I've
already tried.
Thanks in advance for any information,
Torne
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 19 17:22:38 2003