Helge Hafting wrote:
On Sat, Jul 01, 2006 at 08:17:02PM +0200, Tomasz Torcz wrote:
On Sat, Jul 01, 2006 at 07:47:16PM +0200, Thomas Glanzmann wrote:
Hello,
Checksums are not very useful for themselves. They are useful when we
have other copy of data (think raid mirroring) so data can be
reconstructed from working copy.
it would be possible to identify data corruption.
Yes, but what good is identification? We could only return I/O error.
Ability to fix corruption (like ZFS) is the real killer.
Isn't that what we have RAID-1/5/6 for?
I think he is talking about another problem. RAID addresses detectable
failures at the hardware level. I believe that he wants validation after
the data is returned (without error) from the device. While in most
cases if what you wrote and what you read don't match it's memory,
improving the chances of catching the error is useful, given that
non-server often lacks ECC on memory, or people buy cheaper non-parity
memory.
--
Bill Davidsen <[email protected]>
Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
