On 8/3/06, Matthias Andree <[EMAIL PROTECTED]> wrote:
Berkeley DB can, since version 4.1 (IIRC), write checksums (newer versions document this as SHA1) on its database pages, to detect corruptions and writes that were supposed to be atomic but failed (because you cannot write 4K or 16K atomically on a disk drive).
The drive doesn't provide atomic writes for > 1sector (and I'd hardly call trashing a sector during a failed write atomic for even one)... but a FS can provide such semantics.
