I don't think ZFS has any goals of being resilient to errors as far as
recovering from them without backups / redundant disks.... Errors
would still be detected though more data of course would be
unavailable potentially.
On Nov 2, 2009, at 6:04 PM, Chris Samuel wrote:
On Tue, 3 Nov 2009 07:51:52 am Alex Dedul wrote:
In any way thats a nice and interesting feature, thanks! :)
My concern would be that it increases the impact of a corruption of
the block
that has been de-dup'd - in other words if the block that now
represents the
same data in lots of files gets trashed then all those files have
corrupt
data. This implies that you would want to keep around at least one
other copy
of that data to be resilient in the face of corruption (checksums
will let you
detect it, but not necessarily recover from it without duplicate
copies).
Given that ZFS prides itself on detecting errors it would be strange
if they
hadn't considered this in the implementation but I couldn't see any
mention of
it.
cheers,
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
