On 08/14/2013 01:57 PM, Alex Bligh wrote: > I don't agree. The penalty for a qcow2 suffering a false positive on > a change to a backing file is that the VM can no longer boot. The > penalty for your cache suffering a false positive is that the > VM boots marginally slower. Moreover, it is expected behaviour that > you CAN change a backing file if there are no r/w images based on > it. Your cache changes that assumption.
That is right. So when there is a change in the backing file, either the cache should be invalidated or the changes should be propagated to the cache image. If changes to the backing image are not frequent, then invalidation is the simpler approach. In any case, there should be a mechanism to detect this. I assume it is also undesirable for a VM to see stale data when booting from a cow image twice. Kaveh
