You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Harlan Harris <ha...@harris.name> on 2013/09/26 18:18:30 UTC

Re: subversion load fails with “no such revision”

An FYI to all,

I'm back trying to deal with this migration, and it's still a giant mess.
The consistent problem seem to be that revision numbering is just flat
wrong when files were renamed in a revision. I'm fixing "svnadmin load"
errors one-at-a-time by the following process:

1. Find in the dump file the "add" that's breaking. Note that there is a
Node-copyfrom-rev that refers to a revision that doesn't exist in the
filtered file (and is irrelevant in the pre-filtered file); that is, the
revision number is incorrect. Also note that the svnadmin load error
message refers to a third revision number that has nothing to do with the
problem either -- it's NOT the number in the Node-copyfrom-rev.
2. Find the first previous revisionof that file that was a change. Note the
correct revision number.
3. Return to the add that's breaking and manually change
the revision number to refer to that commit.
4. Wipe the repo and restart. Go back to step 1.

I'm doing the load with svnadmin 1.7.13, but the dump was from svnadmin
1.6.6. Upgrading the latter is not an option, which is why we're moving and
splitting the repo.





On Fri, Aug 30, 2013 at 2:03 PM, Harlan Harris <ha...@harris.name> wrote:

> Tony, I used the seemingly-standard version of dumpfilter, not the 2 or 3
> versions. But then I also did the search/replace trick that others had
> suggested to shift paths around. I don't think that's the issue, but I'm
> not sure.
>
> Thorsten, I wish it was just "a bit of web application stuff", but it's
> actually a 5-year-old enterprise repo that was horribly abused, including
> checkins of very large binary and data files. The dump file of the whole
> thing is about 25 GB in size. That's part of why I want to split it up and
> filtering things out.
>
> I'm going to try just exporting the last month worth of revisions, and see
> if that works better. We may have to sacrifice most history in the interest
> of actually getting this working.
>
>  -Harlan
>
>
>
> On Fri, Aug 30, 2013 at 11:41 AM, Thorsten Schöning <tschoening@am-soft.de
> > wrote:
>
>> Guten Tag Harlan Harris,
>> am Freitag, 30. August 2013 um 17:10 schrieben Sie:
>>
>> > I guess disk space is cheap now...!
>>
>> It's especially cheaper than your time if you only need to version "a
>> bit of web application stuff" and, depending on the version of your
>> old repos, newer repos may even reduce disk space because of
>> representation sharing and some improvements in storing directory
>> structures in Subversion 1.8.
>>
>> Mit freundlichen Grüßen,
>>
>> Thorsten Schöning
>>
>> --
>> Thorsten Schöning       E-Mail:Thorsten.Schoening@AM-SoFT.de
>> AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
>>
>> Telefon...........05151-  9468- 55
>> Fax...............05151-  9468- 88
>> Mobil..............0178-8 9468- 04
>>
>> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
>> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>>
>>
>

Re: subversion load fails with “no such revision”

Posted by Andreas Mohr <an...@lisas.de>.
Hi,

On Thu, Sep 26, 2013 at 12:18:30PM -0400, Harlan Harris wrote:
>    An FYI to all,
>    I'm back trying to deal with this migration, and it's still a giant mess.
>    The consistent problem seem to be that revision numbering is just flat
>    wrong when files were renamed in a revision. I'm fixing "svnadmin load"
>    errors one-at-a-time by the following process:
>    1. Find in the dump file the "add" that's breaking. Note that there is a
>    Node-copyfrom-rev that refers to a�revision�that doesn't exist in the
>    filtered file (and is irrelevant in the pre-filtered file); that is, the
>    revision number is incorrect. Also note that the svnadmin load error
>    message refers to a third revision number that has nothing to do with the
>    problem either -- it's NOT the number in the Node-copyfrom-rev.�

I'm not entirely convinced that manual corrections are the way to go.
From the sounds of it, this is a painfully huge effort for you,
with considerable complications. IOW: ouch.

So, AFAICS (you hinted at that) these dumps were split out via svndumpfilter.

What about tending towards trying to fix the suspected root cause
(problematic algorithms in svndumpfilter) rather than huge manual efforts
of trying to fix each such "broken rename" case?

I don't know how difficult/challenging it would be to try to fix
svndumpfilter algorithms to correctly handle/take into account such renames
(I don't have any experience with svndumpfilter),
but to me it sounds like this would be much more lucrative.

If one managed to do some investigations about the differences between
the 4 different svndumpfilter "offsprings" and codify this into a nice
well-manageable upstream project (SourceForge, github, ...)
while fixing the revisions-with-renames issues,
then this would be a huge win AFAICS.


I'm trying to teach the TFS Plain-Original-Software some new SVN tricks,
so I know that there's quite some effort required to achieve proper SCM
handling, but fixing one isolated issue (let's hope it's only one issue...)
hopefully wouldn't be too hard (in the TFS support case there were many
low-hanging fruits, too).

Or try to ask someone to have a look at what would be required
to get these svndumpfilter issues improved...

HTH,

Andreas Mohr