qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Frank Arnold <frank.arnold@amd.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] EXT3-fs error on Git HEAD
Date: Fri, 10 Jul 2009 14:34:48 +0200	[thread overview]
Message-ID: <4A573568.70800@amd.com> (raw)
In-Reply-To: <4A49D5E2.4070705@redhat.com>

Hi,

can someone please apply the patch below from Kevin?
I know that QCOW1 is kind of deprecated, but this should not mean that 
such serious errors stay unfixed. I have this patch in all, well: almost 
  :-( of my branches and would love to see it upstream.
And yes, we are about to convert our images to QCOW2...

Thanks!

Regards,
Andre.


Kevin Wolf wrote:
> Frank Arnold schrieb:
>> Am Montag, den 29.06.2009, 13:42 +1000 schrieb Erik de Castro Lopo:
>>> Erik de Castro Lopo wrote:
>>>
>>>> I have a number of Qemu VMs. Over the weekend I updated to the latest
>>>> Git head and now two of my VMs (one i386 and one x86-64) are having
>>>> disk errors. Strange thing is, my arm VM is working flawlessly.
>>> These VM disk images are all qcow. The i386 and x86-64 ones I converted
>>> to qcow2 and they now work fine. The arm one is still qcow and is still
>>> working fine.
>> We're seeing the same on qemu-kvm.git. I tracked it down to following
>> commits:
>>
>> commit c16b5a2ca0b186de618654a576bdad9cdd2d1ab2
>> Author: Christoph Hellwig <hch@lst.de>
>> Date:   Mon May 25 12:37:32 2009 +0200
>>
>>     fully split aio_pool from BlockDriver
>>
>> commit ad53089b0d0b4bc0731d978e5713365e1a91ba74
>> Author: Christoph Hellwig <hch@lst.de>
>> Date:   Mon May 25 15:45:37 2009 +0200
>>
>>     qcow: add qcow_aio_setup helper
> 
> This one has an obvious bug. Does the following change help?
> 
> diff --git a/block/qcow.c b/block/qcow.c
> index 55a68a6..7fc85ae 100644
> --- a/block/qcow.c
> +++ b/block/qcow.c
> @@ -723,7 +723,7 @@ static BlockDriverAIOCB
> *qcow_aio_writev(BlockDriverState *bs,
> 
>      s->cluster_cache_offset = -1; /* disable compressed cache */
> 
> -    acb = qcow_aio_setup(bs, sector_num, qiov, nb_sectors, cb, opaque, 0);
> +    acb = qcow_aio_setup(bs, sector_num, qiov, nb_sectors, cb, opaque, 1);
>      if (!acb)
>          return NULL;
> 
> Kevin
> 
> 
> 

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448 3567 12
----to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy; Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

      parent reply	other threads:[~2009-07-10 12:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-28 23:50 [Qemu-devel] EXT3-fs error on Git HEAD Erik de Castro Lopo
2009-06-29  3:42 ` Erik de Castro Lopo
2009-06-29  6:42   ` Filip Navara
2009-06-29 16:27   ` Frank Arnold
2009-06-30  9:07     ` Kevin Wolf
2009-06-30 13:32       ` Frank Arnold
2009-07-10 12:34       ` Andre Przywara [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A573568.70800@amd.com \
    --to=andre.przywara@amd.com \
    --cc=anthony@codemonkey.ws \
    --cc=frank.arnold@amd.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).