The bdb backend has 'dbnosync' off by default which means that changes
should be sync'd to disk immediately. I think you may have a problem
elsewhere. Did you try to dbrecover? When dbnosync is off, what does
checkpoint do, exactly? My best guess is that it writes a checkpoint,
which may mean you don't have to dbrecover but at the same time,
everything between that checkpoint and the time the machine crashed
would be lost.
This bug isn't 'critical'. It might be normal, maybe.
Greetings,
The bdb backend has 'dbnosync' off by default which means that changes
should be sync'd to disk immediately. I think you may have a problem
elsewhere. Did you try to dbrecover? When dbnosync is off, what does
checkpoint do, exactly? My best guess is that it writes a checkpoint,
which may mean you don't have to dbrecover but at the same time,
everything between that checkpoint and the time the machine crashed
would be lost.
This bug isn't 'critical'. It might be normal, maybe.
Stephen