Am 27.02.2015 um 20:54 hat Max Reitz geschrieben: > When allocating a new cluster, the first write to it must be the one > doing the allocation, because that one pads its write request to the > cluster size; if another write to that cluster is executed before it, > that write will be overwritten due to the padding. > > See https://bugs.launchpad.net/qemu/+bug/1422307 for what can go wrong > without this patch. > > Cc: qemu-stable <qemu-sta...@nongnu.org> > Signed-off-by: Max Reitz <mre...@redhat.com> > --- > v3: Hopefully finally found the real issue which causes the problems > described in the bug report; at least it sounds very reasonable and > I can no longer reproduce any of the issues described there. > Thank you, Paolo and Stefan!
Thanks, applied to the block branch. Kevin
