1 Feb
2008
1 Feb
'08
4:53 a.m.
Aaron Richton writes:
In the meantime, thanks for the db_dump idea; I can now show that the bad commits are definitely (a) 2.3.40 and (b) increasing.
Can db->set_flags(db, DB_CHKSUM) help narrow it down? It's not a database environment flag, for some reason. http://www.oracle.com/technology/documentation/berkeley-db/db/api_c/db_set_f...
Not relevant for this ITS, but if it's made a slapd.conf option instead of just a hack for this occasion it would likely be useful to offer a way to say "turn it on if DB page size differs from filesystem block size", since that's one case when Berkeley DB can't guarantee that data remains correct: http://www.oracle.com/technology/documentation/berkeley-db/db/ref/transapp/r...
--
Hallvard