Johnathan Gifford wrote:
> I'm in the middle of planning an upgrade of our Subversion server from
> 1.3.0 to 1.4.0. While attempting to dump the current repository so I
> can load into a '1.4.0' repository I came across this.
> svnadmin: Malformed file
> Okay, got my attention, so did some checking with the book and tried
> svnadmin verify. Same error on the same revision number. Not much on
> this has been posted here on the mail list about this issue and I found
> only one link on Google with any hope. That one link did say to check
> revision file from the revprops directory in the db directory of the
> repository. The file was garbage and not clear text. The same holds
> true for the revs directory.
> I would roll back each revision, but this revision happened months ago,
> so that's about 5000 revisions, so this is not very practical and
> beside, all my incremental dumps with the exception of the last week are
> gone. The repository is fine and fully functional in production. But
> since svnadmin verify failed, this has me wondering how many more
> revisions are bad after the first one encountered. I do have the commit
> notification e-mail indicating what the user did.
> So what is an admin to do? Any suggestions on how to get my repository
> dumped using svnadmin dump? Any suggestions how to fix the garbage
> revprops and revs file?
I actually came upon this same exact problem with our main repository
this morning while doing the same thing you were.
I think I've found a way to get around our malformed file, but the
workaround takes advantage of the fact that the revision that is corrupt
is r200 and from about a year ago. HEAD is now at r6700. What we're
planning on doing is running:
$ svnadmin dump -r201:HEAD repositoryName > dump.svn
$ svnadmin create repositoryName2
$ svnadmin load repositoryName2 < dump.svn
$ mv repositoryName repositoryName_20061004
$ mv repositoryName2 repositoryName
Basically, we're just going to throw out those first 200 revisions
since, at this stage of development, they don't really matter much at
all. The only problem I can see with doing it this way is that all of
the revisions will now be skewed by 200 from what they used to be; r5000
will be r4800. I haven't tested doing the load into a new 1.4
repository. Only into one of the same version that it is already as we
have not upgraded yet.
Hope this helps if only a little.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Oct 4 22:01:15 2006