From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Avi Kivity <avi@qumranet.com>,
qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] qemu-img commit -- is there a limit on file sizes?
Date: Mon, 01 Dec 2008 19:58:49 +0200 [thread overview]
Message-ID: <493425D9.5070402@redhat.com> (raw)
In-Reply-To: <49341B60.3090306@codemonkey.ws>
Anthony Liguori wrote:
>
> We've started getting some reports of corruption on "commit" in KVM.
> There is a long standing disk corruption issue too that is very
> difficult to reproduce. The thinking is that there is a bug somewhere
> in the qcow2 code.
>
> Is anyone actively looking into this?
>
I am, though my actively is a lot less than could be desired.
Additional eyes would be welcome.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-12-01 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 1:40 [Qemu-devel] qemu-img commit -- is there a limit on file sizes? walt
2008-12-01 17:14 ` Anthony Liguori
2008-12-01 17:58 ` Avi Kivity [this message]
2008-12-02 0:47 ` walt
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=493425D9.5070402@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@qumranet.com \
--cc=kvm@vger.kernel.org \
--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).