On 2017-08-01 23:00, Christoph Anton Mitterer wrote: > Hi. > > Stupid question: > Would the write hole be closed already, if parity was checksummed? No. The write hole problem is due to a combination of two things: a) misalignment between parity and data (i.e. unclean shutdown) b) loosing of a disk (i.e. disk rupture) Note1: the write hole problem happens even if these two event are not consecutive. After the disk rupture, when you need to read a data from the broken disk, you need the parity to compute the data. But if the parity is misaligned, wrong data is returned. The data checksum are sufficient to detect if wrong data is returned. The checksum parity is not needed. In any case both can't avoid the problem. > Cheers, > Chris. > BR G.Baroncelli -- gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it> Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5 -- 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
