svnadmin didn't report any broken, all passed verification. --- On Sat, 4/2/11, Stefan Sperling <[email protected]> wrote:
> From: Stefan Sperling <[email protected]> > Subject: Re: svnsync sync failure > To: "Jesse Liu" <[email protected]> > Cc: [email protected] > Date: Saturday, April 2, 2011, 12:11 AM > On Fri, Apr 01, 2011 at 03:01:38PM > +0800, Jesse Liu wrote: > > Dear SVN developers, > > > > I met a svnsync interruption error during sync like: > > "Failed to get lock on destination repos, > currently held by 'cn1dg04hpc:e7a198cf-eb76-be41- > > bdb7-336940434069' > > ... > > svnsync: Couldn't get lock on destination repos after > 10 attempts" > > See this bug report and the email threads linked from > there: > http://subversion.tigris.org/issues/show_bug.cgi?id=3546 > > > > > and the log info shows: > > 1)"Could not CHECKOUT resource > /svn/Home/!svn/ver/364/200_Product_Management/270_B_Projects/270_1 > Sundial_Inverter > > prototype/Components/TDK 2.2KW DC-DC. [409, #0] > > [client 140.231.201.98]" > > > > 2)"Unable to fetch the node revision id of the version > resource within the revision. [409, #160013] > > [client 140.231.201.98]" > > > > I tried the normal way to del sync-lock to execute > "svn propdel svn:sync-lock --revprop -r 0 <mirror > repos>" but didn't work, the error info when tried to > sync is: > > > > "Transmitting file data ............svnsync: Error > retrieving replay REPORT (160013): APR > > does not understand this error code" > > > > I use "svnadmin verify" the repository, all passed > until the last reversion before interupted, I have no idea > here,could you help to have a look? thanks very much. > > It could be that you have a corrupted revision in the slave > repository. > Does svnadmin verify report a broken revision or not? >
