I would appreciate being pointed to any sort of in-depth documentation on how the write intent bitmap works. To make my question quick, I'm wondering how the write-intent bitmap holds up to writeback caching. It seems like md would assume that the cached writes had made it to disk, and only rebuild writes that happened since the disk was removed, leaving an inconsistent array. -- 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
