----- John Felczak <email@example.com> wrote:
> Trying to load dumpfile from one server onto another I get the
> following exasperating error:
> [root@jeeves svndumps]# svnadmin load /home/svnroot <
> svnadmin: Dump stream contains a malformed header (with no ':') at '*
> Dumped revision 0.'
> Same version of subversion on both machines:
> [root@jeeves svndumps]# svnadmin --version
> svnadmin, version 1.4.0 (r21228)
> compiled Oct 9 2006, 16:50:24
> Copyright (C) 2000-2006 CollabNet.
> Subversion is open source software, see http://subversion.tigris.org/
> This product includes software developed by CollabNet
> The following repository back-end (FS) modules are available:
> * fs_fs : Module for working with a plain file (FSFS) repository.
> Both are using fsfs. Both machines run linux, so can't be a CR/LF
The dump files are binary, so CR/LF isn't a factor.
> When I look in the dumpfiles they contain normal-looking ASCII text
> with no garbage characters.
You will see normal text in there, but there are also delta streams in there that are completely binary.
> Here's what it looks like in the area around where it's complaining
> K 8
> V 27
> * Dumped revision 0.
This part is wrong. You must have piped both stdout and stderr into the dump file. You need to remove these "* Dumped revision Xxx." lines. Keep in mind that the dump files are binary, so you need to exercise caution when editing your dump file.
> Revision-number: 1
> Prop-content-length: 112
> Content-length: 112
> K 7
> V 38
> New repository initialized by cvs2svn.
> K 8
> V 27
> This has got me very concerned, since if svnadmin can't load its own
> dumpfiles, that means I can't backup my repository with any assurance
> of being able to restore it.
> John J. Felczak
> Build & Integration Manager
> Acting IT Manager
> Siderean Software, Inc.
Subversion is absolutely capable of loading it's own dump files... if you don't mix text that was meant for the screen into them. :-)
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Nov 16 09:20:58 2006