John Locke <mail@freelock.com> writes:
> [root@foraker svnbackup]# svnadmin dump -r 237:246 --incremental
> /var/svn/repos > repos.try
> * Dumped revision 237.
> WARNING: cmp_rev 197 is older than oldest dumped rev 237
> ... loading this dump into an empty repository will fail.
> * Dumped revision 238.
> <snip>
>
> This has happened with every backup containing revision 237, even if I
> make the revision range lower or higher. What does it mean?
It means that r237 contains a "copy" of some other file or directory.
You're dumping r237 all by itself, which means the dumpfile contains a
pointer to data in some earlier revision that is *not* present in the
same dumpfile. So the warning is, "hey, if you try to load this
dumpfile alone, it's not going to have all the data it needs." Of
course, if you load it into a repository that already has revisions
0-236, it will work just fine.
> Part II: I discovered, going through this, that my script was starting
> with the last revision number, not the next one in the sequence. For
> example, a weekly backup dumped up to (and including) revision
> 237. The daily one is starting with 237. If I load these two dumps,
> revision 237 will get passed in twice. Does svnadmin load discard the
> extra deltas when it sees they've been applied, or will I get
> unpredictable results here?
I imagine you'll get some very weird results.
> ... and one more question while I'm at it. I'm very confused by all of
> the log files, and the svnadmin archive/lsdblog/whatever it's called
> now. What should I be doing on a regular basis to clean out
> unnecessary log files? There's several hundred in my biggest
> repository now.
Read the FAQ:
http://subversion.tigris.org/project_faq.html#bdblogs
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 4 22:11:57 2003