Thank you for your reasoned and detailed response and subsequent followup.
This was exactly what I was hoping for.
I'm curious, have you read, *End-to-end Data Integrity for File Systems: A
ZFS Case Study
Zhang, et al?
Abstract: present a study of the effects of disk and memory corruption on
> file system data integrity. Our analysis focuses on Sun's ZFS, a modern
> commercial offering with numerous reliability mechanisms. Through careful
> and thorough fault injection, we show that ZFS is robust to a wide range of
> disk faults. We further demonstrate that ZFS is less resilient to memory
> corruption, which can lead to corrupt data being returned to applications
> or system crashes. Our analysis reveals the importance of considering both
> memory and disk in the construction of truly robust file and storage
...memory corruptions still remain a serious problem to data integrity. Our
> results for memory corruptions indicate cases where bad data is returned to
> the user, operations silently fail, and the whole system crashes. Our
> probability analysis shows that one single bit flip has small but
> non-negligible chances to cause failures such as reading/writing corrupt
> data and system crashing.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/groups/opt_out.