Corrupted revisions - need help

[Gunther Mayer]

Hi there,

I'm the sysadmin for our small company (8 employees) and we're running 
all our shared files over a subversion server. Some time ago our server 
had faulty memory which resulted in corrupt entries being written to the 
underlying fsfs db, later propagating to backups too. This resulted in 
four corrupt revisions in my /var/svn/myrepo/db/revs/XXXX, one of which 
I managed to fix manually with fsfsverify and a whole lot of 
hacking/fudging. The other three however are beyond me and I can't 
afford to spend days of trying to figure out how to fix it (and 
fsfsverify can't do it either, it keeps choking on the same issue). The 
problem is that I cannot take a full backup of my repository or create a 
new working copy from scratch as any command (e.g. svnadmin verify, svn 
co etc.) that comes across these revisions chokes and dies, always with 
the dreaded "Decompression of svndiff data failed" error.

So, I'm wondering if anyone from the community can help me. I think I 
still have all of the original files which got written or amended during 
the three broken revisions (in one or more working copies), but one of 
these revisions is about 1.5GB so sharing is a bit tricky (the other two 
are 23MB and 1.7MB). I'm even willing to pay somebody to do the job if 
that's what's necessary, I only want to recreate my repository from 
scratch as a LAST resort as I would lose all of my history.

Gunther