On May 14, 2007, at 06:42, Jonathan Ashley wrote:
> I've been using svnsync to copy a large-ish repository between two
> machines. I've discovered that svnsync can occasionally hit a revision
> that it can't deal with, in which case it quits with the message
>
> svnsync: REPORT request failed on 'http://src-server/svn/repo'
> svnsync: REPORT of 'http://src-server/svn/repo': 200 OK
> (http://src-server)
>
> In this case, the distinguishing feature of the revision appears to be
> that it was seven gigabytes in size - for now, I'm assuming that's
> what
> causes the failure. (Using SVN 1.4.3, Apache 2.0.59 on Windows 2003.)
Apache 2.0.x uses APR 0.9.x which either does not support revisions
(or other files) greater than 2GB, or at least does not support them
well. Upgrade to Apache 2.2.x with APR 1.2.x and a version of
Subversion compiled with APR 1.2.x.
> To work around it, I used 'svnadmin dump' and 'svnadmin load' to copy
> the troublesome revision manually. Then I incremented the
> 'svn:sync-last-merged-rev' revprop on revision 0 of the destination
> repository, before resuming svnsync. So far this seems to be working,
> but I'm worried that I've missed some subtle aspect of this which will
> cause the repository mirroring to be out-of-sync somehow. Is this kind
> of hacking around with svnsync and svnsync revprops acceptable, or
> does
> it break things?
I'm surprised that worked.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 14 21:00:11 2007