On 19/02/15 14:39, Adam Goryachev wrote: > From memory, there are filesystems which will do what you are asking > (check that the data received from disk is correct, use multiple 'disks' > and ensure protection from x failed drives, etc. I am certain zfs and > btrfs both support this. (I've never used either due to stability > concerns, but I read about them every now and then....) When I used Pr1mes, I don't remember whether it was hardware or software, but I believe their drives implemented some form of parity check and recovery. Basically, every eight-bit byte you wrote went to disk as sixteen bits - a data byte and a parity byte. I don't know how it worked but (1) you could reconstruct either byte from the other, and (2) for any 1-bit error you could tell which of the data or parity bytes was corrupt. For any 2-bit error I think you had a 90% chance of telling which byte was corrupt - something like that anyway. Of course, that's no use if your hacker feeds their corrupt stream through your parity mechanism, or if 0x00000000 is valid when read from disk. Cheers, Wol -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
