On Fri, Sep 30, 2011 at 8:00 PM, PR <rp0013_at_gmail.com> wrote:
> Hello,
>
> I had initially got a lot of great feedback from the group.
>
> I had decided to migrate the repo using the svnsync and the new server is
> 1.7 rc3 for the POC migration. (old server 1.4.6).
>
> Initially every thing was smooth now we are noticing that some
> repositories
>
> we get a failure in sync and that fails with following error
>
> svnsync: E000022: Commit created rev 3912 but should have created 3913
>
> and what i notice is that the 3912 on the source is actually missed and the
> 3913 comes in as 3912 ..on the target repo ..
> the other thing is that this rev is saved as root .. (since i am running as
> sudo, the post rev prop has not got a chance to change it to the actual
> owner ) ..
Then you have a *big* problem. dump/load, rsync, and svnsync are *not* going
to be able to solve this for you. This is a problem with any system that
relies on assembling a long chain of differences together to assemble
complete objects. If you lose a single step of the re-assembly, you don't
have redundancy or error checking or anything to recover the data with.
All may not be lost, however. Can you check old backups to find the
revision? Or can you rsync the old repo over to the new server, simply to
*experiment* with, and try running the svnsync against a local copy of thee
files, in case any mismatches between the 1.4.x version of subversion and
the 1.7.x pre-release, not yet production code you're using are generating
the error.
Last obvious step is to insert a blank revision.....
Received on 2011-10-01 16:52:23 CEST