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

locks caused by aborted svnsync session cannot listed or released

From: Jonathan Coles <jcoles0727_at_rogers.com>
Date: Sun, 21 Sep 2008 19:35:30 -0400

An svnsync session to a mirror repository on my machine was aborted. On
retry I get the error message, "Failed to get lock on destination repos,
currently held by ...".

I tried to use svnadmin lslocks on the repository path. It returns
nothing. How obtuse! There are locks on that repository! I tried an
svnadmin rmlocks on the repository. Response: "No paths to unlock
provided". The repository path is all I have as the location of the
lock. What does svnadmin want?

There are other commands for displaying and releasing locks, but they
require a working copy. All I have is two repositories, the remote one
which is the source and my mirror repository, the destination.

To recap: *svnsync* says that there are locks. *svnadmin* says there are
none. Mirroring of the repository is no longer possible. Is there a way
out, short of destroying the destination repository and starting over?

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-22 01:36:09 CEST

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

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