On Thursday 22 January 2004 13:12, you wrote:
> On Thursday 22 January 2004 06:58, Edmund Horner wrote:
> > Marc Haisenko wrote:
> > >Hi folks,
> > > I've got a problem with dumping our svn repository. svnadmin dump
> > > always gives this error message:
> > >
> > >...
> > >* Dumped revision 333.
> > >* Dumped revision 334.
> > >* Dumped revision 335.
> > >svn: txn_body_read_rep: checksum mismatch on rep "4pe":
> > > expected: 92008dd3fc9fde82d9b5b1b0bc79db6b
> > > actual: 8e4edf81c57f3ba3a318630a89f4f762
> > >
> > >But the repository works just fine (current revision in repository is
> > > 411). I haven't tried svnadmin recover yet since I'm not sure whether
> > > there is something broken, normal svn operation works just fine. And if
> > > it ain't broke, don't fix it ! ;-)
> > >
> > >Any idea what's wrong here ?
> This means that some data in the repository is corrupted, but not bad
> enough to damage the structure of the repository itself. Do you have any
> idea what happened around that time frame?
> > Have you tried "svnadmin verify" ?
> Actually, "verify" is "dump". :-) Seriously, the only thing it does it not
> pipe the data to stdout.
I've tried it anyways :-) And it really finishes without problems.
> > If verify comes up with no problems, then something odd is happening.
> > But if verify also finds the mismatch, then I think that part of the
> > string data for r335 is broken. If there are other revisions after r335
> > that replace that data, then you probably won't have noticed it in
> > normal use.
> > You can examine that end of the partial dumpfile to find the affected
> > path.
So I should do an svnadmin dump -r335:336 or something like that ?
> > AFAIK, "svn recover" doesn't fix data errors like this.
> From my understanding, this is correct too.
Webport IT-Services GmbH
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Jan 22 13:29:45 2004