On 06/08/12 11:53, Asdo wrote:
.....
Then I tried to do :
for i in /dev/md? /dev/sda /dev/sdb ; do blockdev --flushbufs $i ; done
....
and NOW it is seeing the changes.
After some further tests:
Flushbuf'ing just the MD devices only, generated an even more
intermediate situation in which the file being changed assumed garbage
content coming from another old file.
Flushbufing just /dev/sda /dev/sdb has worked a few times I tried. I'm
not sure that it is enough in general.
Flushbufing everything appears to work reliably.
Still I am puzzled. Wasn't "sync" from bash enough to commit to disk
even in case of power failure?
Or is there any chance that KVM "sees" a version of sda and sdb which is
actually *older* than the actual content on the platters?
Thank you
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
