| |||||||||||||
The 2006 Linux Filesystems Workshop (Part II)The 2006 Linux Filesystems Workshop (Part II)Posted Jul 7, 2006 9:10 UTC (Fri) by sveinrn (guest, #2827)In reply to: The 2006 Linux Filesystems Workshop (Part II) by vaurora Parent article: The 2006 Linux Filesystems Workshop (Part II)
I have looked at it. But as far as I can see, this scheme does not protect proberly against '"high-flying writes" and "over-powered seeks", "phantom writes" and "misdirected reads and writes."'
The parity schemes used in RAID are good for recreating data that is known to be missing. Error correcting codes (including the Hamming code) are good for correcting data that is readable but corrupt. So my first thought was that with RAID6 on top of the Hamming code we would be protected from 2 failed disks in combination with 1 corrupt disk. But that is clearly wrong. So a better idea could be one of the more modern codes, for example the Reed-Solomon code. That also removes the need for RAID6 parity on top. (The Reed-Solomon code is also especially effective when one knows where the error is, i.e. a missing disk.)
(Log in to post comments)
|
|||||||||||||