Goswin von Brederlow wrote:
The check is usualy done with the filesystem mounted and in use. So one
case would be that the block got written, changed and then checked
before the FS decided to flush the dirty block again.
The other scenario suggested in the past is that the block was written,
changed and then the file deleted, making the block unused,
This is not enough to cause the problem if I understand correctly, it
also needs to change value at this point, right?
So how can it change value... is the same buffer used for another block?
before it
got flushed again. The filesystem then sees no need to write a dirty but
unused block so it never gets rewritten. It never gets read either so
that is safe.
--
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
