On Sep 12, 2006, at 4:39 PM, Celso wrote:
On 12/09/06, Celso <[EMAIL PROTECTED]> wrote:
I think it has already been said that in many
peoples experience, when a disk fails, it completely
fails. Especially on laptops. Of course ditto blocks
wouldn't help you in this situation either!
Exactly.
I still think that silent data corruption is a
valid concern, one that ditto blocks would solve. >
Also, I am not thrilled about losing that much space
for duplication of unneccessary data (caused by
partitioning a disk in two).
Well, you'd only be duplicating the data on the
mirror. If you don't want to
mirror the base OS, no one's saying you have to.
Yikes! that sounds like even more partitioning!
The redundancy you're talking about is what you'd get
from 'cp /foo/bar.jpg /foo/bar.jpg.ok', except it's
hidden from the
user and causing
headaches for anyone trying to comprehend, port or
extend the codebase in
the future.
the proposed solution differs in one important aspect: it
automatically detects data corruption.
Detecting data corruption is a function of the ZFS checksumming
feature. The proposed solution
has _nothing_ to do with detecting corruption. The difference is in
what happens when/if such
bad data is detected. Without a duplicate copy, via some RAID level
or the proposed ditto block
copies, the file is corrupted.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
