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

Re: How to solve svnadmin load "File already exists" error?

From: Konstantin Kolinko <knst.kolinko_at_gmail.com>
Date: Wed, 24 Aug 2011 02:30:06 +0400

2011/8/23 Dennis Jones <djones_at_grassvalleysoftware.com>:
>> I tried to edit a 5 Gb file on a Linuxserver we have with vi, it took some
>> 30 minutes to open the file but it did work!
>>
>> The format is quite simple :  a revision starts with the string :
>>
>> Revision-number:
>>
>> Just delete all the lines  until the next
>>
>> Revision-number:
>>
>>
>> And the revision is removed from the dump. I am not quite sure if you need
>> to renumber the revisions afterwards though, but I
>> don't think so.
>>
>> There is a problem though if what you delete is referenced later on in the
>> dump, then the load will fail.
>
>
> Unfortunately, this did not work.  I was able to split the file into
> smaller, editable pieces, cut out the bad revision, and paste it all back
> together.  However, when I attempted to start loading at the revision
> following the bad one, I got checksum mismatches.

Apparently you cannot edit the dump file with vi.

It is mentioned somewhere in the SVN Book that the dump just looks
like a textual file but actually it is binary. It explicitly does not
recommend editing it in a text editor. (So the problem with checksums
that you are facing is documented).

Can you generate a dump file for a range of revisions? Looking at [1]
you can specify a range of revisions to be dumped by rsvndump tool.

[1] http://rsvndump.sourceforge.net/

Have you tried to compare old and new repository at revision 3186.
E.g. do a checkout and compare whether files and folders all exist and
are the same?

Especially the files and folders touched by r3187.

Best regards,
Konstantin Kolinko
Received on 2011-08-24 00:30:50 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.