On Thu, Apr 08, 2010 at 06:28:54PM +0300, Avi Kivity wrote: > When it updates qcow2 metadata or when the guest issues a barrier. It's > relatively new. I have a patch that introduces cache=volatile somewhere.
qcow2 does not issues any fsyncs by itself, it only passes throught the guests ones. The only other placess issueing fsyncs is commit a COW image back to the base image, and on migreation. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
