[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

corruption in fsfs binary file svnadmin: Checksum mismatch,

From: Karl Hiramoto <karl_at_hiramoto.org>
Date: Mon, 20 Oct 2008 18:54:50 +0200

Hello,

 I can't find anything in the FAQ or book on how to solve this:

 cat /tmp/svn.dump.20081010b |svnadmin load test

------- Committed revision 1789 >>>

<<< Started new transaction, based on original revision 1790
svnadmin: Checksum mismatch, file '/path/to/file/binary.zip':
   expected: 8df02db10cec51a3a3124d5559e45686
     actual: d7ff14845ae7ef5c891815e38e3c3e44

     * adding path : /path/to/file/binary.zip ...

A few notes:

1. My repository is about 4-5 years old and svb has been upgraded a
few times over the years.

2. Currently the entire repository is about 3GB

3. Commit 1790 (where the problem is) was done a few years ago. I
can live without this zip file. But i would like to keep the rest of
the files and history of the other stuff if possible.

4. The repository has in total 4200 revs.

5. I recycle/reuse my backup media every few months so i can't go back
for an old version of the file /var/svn.backup/db/revs/1790

6.. I'm trying to dump on an old machine with version 1.4.6, and load it
on a new one with 1.5.1 I've also tried loading/dumping with both 1.4.6
and 1.5.1

  I have seen in the archives people talking about manually editing the
md5sum to be all 00's and it looks easy for a text file, but I don't
know how you see it, or which editor to use on the binary file

/var/svn.backup/db/revs/1790

Can someone tell me, or point me to a HowTo resolve this issue.

Thanks...

--
Karl Hiramoto  http://karl.hiramoto.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-20 18:55:25 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.