On Fri, Jul 23, 2010 at 12:43:14PM +0200, Jan Kara wrote: > changelog below. I'd much rather attribute the metadata corruption to a missing > barrier option or barrier support in the virtualization stack. But I guess it's > hard to tell now. Any recent qemu/kvm stack has perfectly working barrier support. Xen is quite broken in that respect, but I hope no one is using that anyway. But yes, with large write caches ext3 is rather broken due to the lack of barriers. Fortunately enough at least the enterprise enable it anyway these days. -- 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
