Is there any plan to move the package with the fix to the stable branch? It looks like the bug appears in other use cases, as well:
https://bugs.launchpad.net/ironic/+bug/1490086 https://review.openstack.org/#/c/218882/ Thanks. Mario On Mon, Aug 31, 2015 at 7:45 AM, Debian Bug Tracking System <ow...@bugs.debian.org> wrote: > This is an automatic notification regarding your Bug report > which was filed against the qemu-utils package: > > #797221: qemu-utils: qemu-img fails to write image to RAID device > > It has been closed by Michael Tokarev <m...@tls.msk.ru>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Michael Tokarev > <m...@tls.msk.ru> by > replying to this email. > > > -- > 797221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797221 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > ---------- Forwarded message ---------- > From: Michael Tokarev <m...@tls.msk.ru> > To: Mario Villaplana <mario.villapl...@gmail.com>, 797221-d...@bugs.debian.org > Cc: > Date: Mon, 31 Aug 2015 15:24:12 +0300 > Subject: Re: Bug#797221: qemu-utils: qemu-img fails to write image to RAID > device > Version: 2.2+dfsg-1exp > > 28.08.2015 20:18, Mario Villaplana wrote: >> Package: qemu-utils >> Version: 1:2.1+dfsg-12+deb8u1 >> Severity: important >> >> Dear Maintainer, >> >> I was testing writing a full disk image to disk with qemu-utils within a >> Docker >> container built from Debian Jessie with the qemu-utils package installed by >> running apt-get in the Dockerfile. The disk is configured as an Intel RSTe >> RAID >> 1 (imsm metadata) device built from /dev/sda and /dev/sdb with mdadm. The >> RAID >> volume exists at /dev/md126. >> >> The exact command I ran was this: >> >> qemu-img convert -t directsync -O host_device my_image /dev/md126 >> >> The image fails to write to disk with the following error: >> >> qemu-img: error writing zeroes at sector 0: Invalid argument >> >> I was expecting a successful write to disk. This succeeded previously when we >> based the container off of a version of Ubuntu which shipped qemu-img version >> 2.0.0. >> >> I found a similar bug in RHEL 7 that seems to have been fixed by upgrading >> qemu-img to the latest version: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1196688 >> >> The reporter of that bug suggested that a particular commit in qemu fixed the >> issue. > > This has been fixed in upstream qemu 2.2. > > Thanks, > > /mjt > > ---------- Forwarded message ---------- > From: Mario Villaplana <mario.villapl...@gmail.com> > To: Debian Bug Tracking System <sub...@bugs.debian.org> > Cc: > Date: Fri, 28 Aug 2015 17:18:54 +0000 > Subject: qemu-utils: qemu-img fails to write image to RAID device > Package: qemu-utils > Version: 1:2.1+dfsg-12+deb8u1 > Severity: important > > Dear Maintainer, > > I was testing writing a full disk image to disk with qemu-utils within a > Docker > container built from Debian Jessie with the qemu-utils package installed by > running apt-get in the Dockerfile. The disk is configured as an Intel RSTe > RAID > 1 (imsm metadata) device built from /dev/sda and /dev/sdb with mdadm. The RAID > volume exists at /dev/md126. > > The exact command I ran was this: > > qemu-img convert -t directsync -O host_device my_image /dev/md126 > > The image fails to write to disk with the following error: > > qemu-img: error writing zeroes at sector 0: Invalid argument > > I was expecting a successful write to disk. This succeeded previously when we > based the container off of a version of Ubuntu which shipped qemu-img version > 2.0.0. > > I found a similar bug in RHEL 7 that seems to have been fixed by upgrading > qemu-img to the latest version: > > https://bugzilla.redhat.com/show_bug.cgi?id=1196688 > > The reporter of that bug suggested that a particular commit in qemu fixed the > issue. > > The error does not occur when writing to a single disk (like /dev/sda) without > RAID configured. I believe that upgrading qemu-utils so that the commit > mentioned above is included will fix the issue. > > Thank you for your time. > > -- System Information: > Debian Release: 8.1 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.0.7-coreos-r2 (SMP w/12 CPU cores) > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages qemu-utils depends on: > ii libaio1 0.3.110-1 > ii libc6 2.19-18 > ii libcurl3-gnutls 7.38.0-4+deb8u2 > ii libgcc1 1:4.9.2-10 > ii libglib2.0-0 2.42.1-1 > ii libgnutls-deb0-28 3.3.8-6+deb8u2 > ii libiscsi2 1.12.0-2 > ii librados2 0.80.7-2 > ii librbd1 0.80.7-2 > ii libssh2-1 1.4.3-4.1 > ii libuuid1 2.25.2-6 > ii zlib1g 1:1.2.8.dfsg-2+b1 > > Versions of packages qemu-utils recommends: > pn sharutils <none> > > Versions of packages qemu-utils suggests: > pn debootstrap <none> > > -- no debconf information >
