kfogel@collab.net wrote:
> Dave Littell <davidl@applink.net> writes:
>
>> I upgraded to subversion 1.2 (and went through the BerkeleyDB
upgrade
>> to 4.3 "recovery" process described at the subversion site). Now
>> commits fail with checksum mismatch errors. An "svnadmin
verify" gets
>> all the way to revision 6 (out of over 200) before cratering with
>> another checksum mismatch.
>>
>> It seems pretty clear that the transition to the 4.3 database
>> corrupted my repository. The repository traffic is extremely light
>> (I'm the only one using it for generally (very) small commits)
and all
>> via file:///), so I'm having a hard time accepting that this is
result
>> of intense usage or mixed network/file access.
>>
>> Is there a way to repair the repository?
>
>
>
> Do you still have a backup of the old 4.2 repository?
>
Thank God.
> Frankly, I suggest and end-run around the whole thing -- just convert
> the old repos to FSFS and go from there.
>
I ended up doing a dump on a machine that I hadn't yet "upgraded"
(read screwed up), then a load on the "upgraded" machine.
Isn't this something the Subversion guys said they'd exert every
effort to keep from happening? The blasted release notes for 1.2
should have said - "We jacked this one up totally, so dump and load,
boys, dump and load." Instead, we get "try this - it probably won't
work and it'll trash your repository, but it's no big deal. You
should know better anyway and always, always, always do a full
dump/load for any and every point release."
Now I know better. Either never upgrade or prepare to do a full
dump/load even if it's only a 0.0.1 rev.
I am so extremely glad I haven't "upgraded" my Subversion server at
work - they would have crucified me!
Yes, I am furious over this. The way it was handled stinks out loud.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 5 18:38:23 2005