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

Re: snvsync issues

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Fri, 16 May 2014 11:07:50 +0100

James Cloos <cloos_at_jhcloos.com> writes:

> I occasionally get syncs which are stuck because something killed the
> process before it could release its lock.
>
> The only way I could get past that was to edit revprops/0/0 and remove
> the svn:sync-lock lines.
>
> Is there a command which will remove such stale svnsync locks?

No, and that is deliberate as the lock is the mechanism that stops
multiple svnsync in parallel.

> Neither svn, svnadmin nor svnsync seem to be able to do so. Or even to
> list such locks.

The lock is a revision property and can be seen and deleted like any
other revision property.

> Several of the remote repos which I'd like to sync fail part way through
> with errors like:
>
> svnsync: E210008: Error while replaying commit
>
> Git-svn is able to clone such repos, including the commits which svnsync
> cannot replay, so it doesn't seem to be due to any corruption.

00210008 SVN_ERR_RA_SVN_EDIT_ABORTED

That tells us that the sync is using svn:// but little else. You need to
provided more detail about the changes in the commit that is failing.

> Is there any way past the error, without alternate access to the remote?

You can configure the authentication and hooks for the target repository
to allow the lock to be deleted over the network just like any other
revision property.

-- 
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Received on 2014-05-17 06:27:46 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.