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

Re: svnsync --disable-locking

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Thu, 19 Sep 2013 19:41:25 +0100

Seumas Soltysik <ssoltysi_at_aurea.com> writes:

> I am using svnsync to sync a mirror with a master. However, I am getting
> the following error:
> svnsync: E160039: User 'xxxx' does not own lock on path '/foo/bar'
> I understand why this is happening but I am not sure what the solution is.
> Based upon the svnsync documentation it would appear that the "svnsync
> --disable-locking" option is what I need. However, in my opinion the
> documentation is unclear about what the option does and googling returns
> very little that is helpful.
> Am I correct in believing that the --disable-locking mechanism will ignore
> all user locks on the mirror and allow me to sync the master and mirror and
> thus resolve the error that I am seeing?

No. svnsync uses revision properties to 'lock' the mirror repository to
ensure that only one svnsync process modifies the mirror at any one
time. --disable-locking disables that locking.

svnsync doesn't support Subversion's exclusive file locking. You need
to remove the locks from the mirror. You can use svnadmin's lslocks and
rmlocks or, for an FSFS repository, you could remove the db/locks dir.
You might install a pre-lock hook in the mirror to prevent locks being

Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Received on 2013-09-19 20:42:15 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.