Ok, I looked at the issue. The problem is that the Xen backend drivers are (as expected) utterly braindead and submit bios directly from the virtualization backed without using proper abstractions and thus bypassing all the cache coherency features in the fileystems (the block device nodes are just another mini-filesystem in that respect). So when you first have buffered access in the host pages may stay in cache and get overwritten directly on disk by a Xen guest, and once the guest is down the host may still use the now stale cached data. I would recommend to migrate your cutomers to KVM which uses the proper abtractions and thus doesn't have this problem. There's a reason after all why all the Xen dom0 mess never got merged to mainline. -- 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
