[Bug 1292234] Re: qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)

[Ryan Harper]

can we confirm what filesystems and options are enabled when reproducing
(ie, ext4 +extent mapping)[1] ?  Bug 1368815 sounds very much like this.
If the reproducing systems have ext4 extents mapping enabled, one could
create an ext4 fs without extent mapping[2] and see if this still
reproduces.

If it is related to the ext4 extents, the rate of memory pressure and
speed of the underlying device would determine whether or not the file
ends up being corrupt which might explain the difficulty of reproducing.

1. % sudo tune2fs -l /dev/disk/by-id/dm-name-kriek--vg-root  | grep -i features
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
2. mke2fs -t ext4 -O ^extent /dev/<device>

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1292234

Title:
  qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1292234/+subscriptions