Hi, > When memory changes between being written to one device and to another, this > does not cause corruption, only inconsistency. Either the block will be > written again consistently soon, or it will never be read. well, is this for sure? I mean, by design of the md subsystem. Or it is like that because we trust the filesystem? And why it is like that? Why not to use the good old readers-writer mechanism to make sure all blocks are the same, when they're are written (namely lock). It seems to me, maybe I'm wrong, not a so safe design. I assume, it should not be possible to cause this situation, unless there is a crash or a bug in the md layer. What if a new filesystem will write a block, changing on the fly, i.e. during RAID-1 writes, and then, later, reading this block again? It will get, maybe, not the correct data. In other words, would it be better, for the md layer, to be robust against these kind of threats? bye, -- piergiorgio -- 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
