[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: All long commits fail

From: <kfogel_at_collab.net>
Date: 2003-09-19 17:03:53 CEST

Torne Wuff <torne-svn@wolfpuppy.org.uk> writes:
> 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.

Yes this sounds exactly like

   http://subversion.tigris.org/issues/show_bug.cgi?id=1245

> 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.

At first I thought this was

   http://subversion.tigris.org/issues/show_bug.cgi?id=1431

but the symptom is different. In the above example, there were no
changes in the working copy other than a property change to "."?

Is anyone else using your repository, perhaps making changes down in
the tree (thus making the directories up near the top very likely to
be newer than what any given working copy has)?

If this reproduces

   $ svn st -q
   $ svn propset svn:ignore "...new value..." .
   $ property `svn:ignore' set on ''
   $ svn st -q
   M .
   $ svn ci -N -m "Update ignores."

*even* when no one else is using the repository at all from the start
of the recipe to the end, then yeah, I'd say there's a bug!

-Karl

---------------------------------------------------------------------
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:52:14 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.