For what it's worth, I get the same errors when my Subversion
repository dies, and I'm confident that I have the versions matched
correctly, etc. I'm also on Mac OS X 10.3.4, so that might be what's
throwing people off with the BDB error messages.
Anyway, for guaranteed recoverability, just got to the db directory of
your repository and comment out the line in DB_CONFIG that says
This will keep your log files permanently, which you can backup to disc
if you don't want them to take up space. However, you'll need
(potentially) all of them when BDB needs to recover on Mac OS X. Even
though my repository is corrupted rather regularly, having the full set
of log files has allowed me to recover it every time. Don't trust the
output from db_recover -c. It'll say it failed (and give the same error
message!), but a subsequent verify indicates that it really succeeded,
and that everything is okay (which it is).
I think Subversion is plenty safe for your data. I've also looked at
the source (which I encourage everyone to do). It's clear that the
developers set the quality bar really high.
On Jul 16, 2004, at 10:14 AM, Pejvan BEIGUI wrote:
> Max Bowsher wrote:
>> I suppose it might be possible for Berkeley DB's files to become
>> in such a way that did not affect the data itself, but caused any
>> attempt to
>> allocate more space within those databases to fail.
>> As to what might cause such subtle corruption - I have no idea.
> This BDB thinguy starts to frightening me. And I'm about to install svn
> for a whole team of developers, which frightens me even more now...
> Anyway, it's the right time to make a DVD-RW back-up I believe :-)
> Thanks again for your help.
> Pejvan BEIGUI email@example.com
> Cet email comporte une signature electronique au format OpenPGP/MIME.
> Pour votre propre sécurité, tout email semblant provenir de cette
> adresse mais ne comportant pas de signature ou une signature
> non-valide sera réputé falsifié.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Jul 17 02:42:32 2004