John Peacock wrote:
> Here is your problem. There is something in rev 2573 that is a copy
of
> something at revision 1926, which is outside of your dump window.
Thus
> Subversion won't have any file to copy when it comes to `svnadmin
load`
> this
> file. This will cause a fatal error when loading.
>
> > WARNING: dumped revision (2000). Loading this dump into an empty
> > repository
> > WARNING: will fail.
>
> This is a direct consequence of Subversion's "cheap copy" design.
Perhaps
> if
> you described what you hoped to actually accomplish, rather than
deciding
> a
> priori how you want to accomplish it, we could give you better
advice...
Sure, Thanks! -- My goal is to reduce the size of a large repo by
splitting it into two pieces, an "older" part containing all revs up to
a certain point (e.g. rev 2000) and a "newer" part nominally starting
with a full snapshot of the repo as of the cutoff rev (e.g. 2000) with
all the succeeding deltas.
Note -- I said "nominally", since I understand that a simple snapshot
(or whatever the proper term is) is HUGE due to tags and branches. I
strip out all of the tags and branches active at the cutoff rev using
svndumpfilter3. But this is an efficiency issue, rather than a
repository correctness issue.
So (ignoring the efficiency issue) I assumed the following was a valid
operation:
# svnadmin dump orig-repo -r 2000:9999 > newer.dump
# svnadmin create newer-repo
# svnadmin load newer-repo < newer.dump
Clearly the dump does a lot of processing to create a valid
self-contained image for the first rev it emits. I assumed it kept
track of that processing and suitability modified the remaining revs
too, so that the resulting dump file could be loaded into a virgin repo.
It sounds like that may not true.
If this is not the case, I'm not sure what utility there is for dumping
a range of repositories in the default (non-incremental) mode. The book
certainly describes creating dump files in this way, although I now
realize I cannot find an example therein of using such a dump file. If
these dump files are not valid, why have the option at all, and why
publish examples of their creation?
Lastly, since I do plan to filter the dump file (using svndumpfilter3),
am I safe if the load operation does not emit any warnings?
Puzzled,
-- Charlie
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-20 17:05:01 CET