[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <44D285DF.7060905@elegant-software.com>
Date: Thu, 03 Aug 2006 19:25:19 -0400
From: Russell Leighton <russ@...gant-software.com>
To: Matthias Andree <matthias.andree@....de>
Cc: David Masover <ninja@...phack.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Adrian Ulrich <reiser4@...nkenlights.ch>,
"Horst H. von Brand" <vonbrand@....utfsm.cl>,
bernd-schubert@....de, reiserfs-list@...esys.com,
jbglaw@...-owl.de, clay.barnes@...il.com, rudy@...ons.demon.nl,
ipso@...ppymail.ca, reiser@...esys.com, lkml@...productions.com,
jeff@...zik.org, tytso@....edu, linux-kernel@...r.kernel.org
Subject: Checksumming blocks? [was Re: the " 'official' point of view" expressed
by kernelnewbies.org regarding reiser4 inclusion]
If the software (filesystem like ZFS or database like Berkeley DB)
finds a mismatch for a checksum on a block read, then what?
Is there a recovery mechanism, or do you just be happy you know there is
a problem (and go to backup)?
Thx
Matthias Andree 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).
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists