svnadmin dump: Checksum mismatch while reading representation

Hi all,

I ran across a "Checksum mismatch while reading representation" while
trying to dump a repository with some broken revisions.

The repository youngest revision is 193, and the "checksum mismatch"
happens at revision 125:

   .../svnroot$ svnadmin verify lili.bkp
   [...]
   * Verified revision 125.
   svnadmin: Checksum mismatch while reading representation:
      expected: 547ff6c791c793e8ba1d6b15acb2b14a
        actual: 787975e9ec214489495fe8b7bdafeb5c

Is there a way to dump fix the revision so that I can just dump it, with
or without that revision?

I'd like to restore this repository in a stable state, and restore a
fresh WC for a user (whose files I wiped away while doing multiple
concurrent operations in TortoiseSVN...)

As suggested on the list [1], I thought of zeroing the checksum. The
weird thing is that the expected checksum
'547ff6c791c793e8ba1d6b15acb2b14a' does not appear within the file
svnroot/lili.bkp/db/revs/125:

   .../svnroot$ grep -c 547ff6c791c793e8ba1d6b15acb2b14a
lili.bkp/db/revs/125
   0

fsfsverify.py -f lili.bkp/db/revs/125 did not help [2]. I ran
fsfsverify.py -c lili.bkp/db/revs/125 and could figure out which files
where added. I have a copy of these files and could add them to the
head; I would lose their history, but that would be a minor problem for now.

I also thought of [3]:

   svnadmin dump lili.bkp -r1:124 > revs-1to124.dump
   svnadmin dump lili.bkp -r127:HEAD --incremental >
revs-127toHEAD-incr.dump

however I would lose revision 126, which is a huge 80MB commit.

Any suggestions would be very welcome, I spent hours yesterday searching
the list archives and I ran out of ideas.

--
Olivier
[1] 
http://subversion.tigris.org/servlets/ReadMsg?listName=users&msgNo=54923 
(John Szakmeister)
[2] 
http://subversion.tigris.org/servlets/ReadMsg?listName=users&msgNo=60030 
(John Szakmeister)
[3] http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=40400 
(John Szakmeister)