On Mar 22, 2006, at 03:08, Christopher L Merrill wrote:
>> Do you have up-to-date backups? Dumpfiles?
>
> No. I thought about doing a dump...but since it was _supposed_ to be
> a simple file move, I didn't. My bad :( I guess I should have
> researched
> the quirks of BDB more.
Now would also be a good time then to start doing daily dumps. You
can do them incrementally to save space, maybe doing a full dump only
every week or every month. You can even write a post-commit hook to
make a dump of that revision immediately. There are many
possibilities, but it's certainly important to just pick one, even if
it's not the best solution. An inefficient backup is still better
than no backup.
>> Once you get this sorted out, consider moving the repository to
>> FSFS, since it cannot suffer from these problems. How to do so is
>> in the FAQ.
>
> That is definitely on my list for this weekend.
>
> FWIW, I'm still not sure exactly what instigated this problem, but
> somewhere
> I found advice to delete some log files and then try a recover. As
> it turns
> out, following that advice exaserbated the problem. Once I
> realized that
> for BDB the log files are actually _important_, I simply restored
> the files
> from a backup, did a recover and viola! Everything back to normal.
Yes, they're not log files in the traditional sense of text files
that serve only to inform the administrator later. They're more like
journal files for a journaled filesystem, in which data is written to
the logs first, and only later into the actual DB files, and if you
remove the logs before this happens, you've lost data. There is some
command you can use to get BerkeleyDB to tell you which log files
it's done with and which are safe to remove, but I forget the command
at the moment.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 22 11:33:01 2006