I wanted to post a resolution to my problem here after posting last
week about my corrupt repository. I got input from several people on
this list on how to handle the recovery. And I know a lot more about
SVN than I did before, but what I really learned is that there is no
substitute for expertise.
Here's the problem I had:
I had an FSFS SVN database running on an ISP's server. At some point
the FSFS file system became corrupt (possibly during a cluster/disk
outage that may have occurred while I was updating a file - not sure).
A specific revision, containing (luckily) only a single (large) file
was corrupt. But I couldn't "dump" future revisions using the standard
commands (though all prior versions dumped fine).
My ISP (and I) spent several days poking through old mail list messages
and documentation trying to fix this issue - several people on this
list gave good input as well.
I wrote about my problem to several companies that do commercial SVN
hosting. I got friendly responses back from two that are noteworthy:
Wush.net and csvdude.org - both groups were friendly and offered to
Wush immediately said "send us your file and we'll see what we can do."
I did just that (sending both the correct version of the corrupt file
as well as the entire corrupt repository). They corrected the problem,
and loaded it on their webserver and contacted me within half a day.
I signed up for service with them and am using them now happily. They
didn't ask me to sign up and I didn't ever pay for the consulting time
it took them to correct the problem. They seemed to want to fix the
problem b/c it was broken and _should_ be fixed. I felt it was very
generous of them, whatever their reasons.
Find someone who knows more than you and has the business sense to
treat you right. I'd like to endorse wush.net (and cvsdude) for being
friendly, competent and quick.
I hope this email is helpful for someone else in the future. And thanks
to everyone who provided help to me during this stressful time.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Apr 22 23:57:26 2007