Tested qemu-utils 2.0.0+dfsg-2ubuntu1.8. Successful.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts output images
Status in OpenStack
** Tags removed: verification-needed
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts output images
It seems the dust settles a bit: Found the relevant difference between
my various filesystems, and how to reproduce the failure: Susceptible
filesystems don't have the extent feature of ext4 enabled.
You can create such a filesystem using
mke2fs -t ext4 -O ^extent /dev/...
mount /mnt
The fallback cascade Pádraig mentions is already implemented in
qemu-2.1.0, in function raw_co_get_block_status. Just swap
ret = try_fiemap( ... )
and
ret = try_seek_hole( ... )
to reverse the order. I can confirm that it works just fine on 3.13
kernel (all version since 3.1, according to
The affected code was introduced with version 1.2.0. However, due to
https://bugs.launchpad.net/qemu/+bug/1193628 I can't build these old
releases to verify whether they actually expose the same behaviour.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1368815
Title:
qemu-img convert intermittently corrupts output images
Status in
Public bug reported:
-- Found in releases qemu-2.0.0, qemu-2.0.2, qemu-2.1.0. Tested on
Ubuntu 14.04 using Ext4 filesystems.
The command
qemu-img convert -O raw inputimage.qcow2 outputimage.raw
intermittently creates corrupted output images, when the input image is
not yet fully synchronized
