Comment 14 for bug 8392

Torsten Landschoff wrote:
> I've read up on Berkeley DB transactions and it seems to me that it
> would make sense to write a checkpoint from time to time. No data should
> be lost but in the default configuration slapd only checkpoints the DB
> during shutdown which means that reopening the database after a crash
> (which looks for me like the only reason why slapd would go down short
> of a system reboot) will take a lot of time wading through old log
> files.
>
> I don't want to mess with the slapd defaults for this small problem
> though and I wonder what upstream has to say. AFAICT the checkpoint
> directive leads to a massive breakdown of write performance for not that
> much gain.

I have lost significant data because this directive wasn't in the
logfile, and I didn't know how to recover a berkeley db. The third
time this happened I spent several hours reading up on it and managed to
get my data back. If slapd or the system crashes (in this case it was
because of a power outage), then the database needs to be manually
recovered.

It doesn't happen automatically, so can lead to data loss if the
database is not recovered.

doug.

--
6973E2CF: 2C95 66AD 1596 37D2 41FC 609F 76C0 A4EC 6973 E2CF
http://adju.st/