> On Mon, 2006-10-09 at 15:49 +0200, Erik Mouw wrote: > >> There is no way to figure out what exactly is correct data and what is >> not. It might work right after creation and during the initial install, >> but after the next reboot there is no way to figure out what blocks to >> believe. > > You don't really need to. After a clean install, the operating system > has no business reading any block it didn't write to during the install > unless you are just reading disk blocks for the fun of it. And any > program that depends on data that hasn't first been written to disk is > just wrong and stupid anyway. I suppose a partial-stripe write would read back junk data on the other disks, xor with your write, and update the parity block. If you benchmark the disk, you're going to be reading blocks you didn't necessarily write, which could kick out consistency errors. A whole-array consistency check would puke on the out-of-whack parity data. - 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
