From: Anthony Liguori <anthony@codemonkey.ws>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Revert block-qcow2.c to kvm-72 version due to corruption reports
Date: Sun, 15 Feb 2009 19:19:52 -0600 [thread overview]
Message-ID: <4998BF38.3070605@codemonkey.ws> (raw)
In-Reply-To: <alpine.DEB.1.00.0902151933210.10279@pacific.mpi-cbg.de>
Johannes Schindelin wrote:
> Hi,
>
> On Sun, 15 Feb 2009, Anthony Liguori wrote:
>
>
>> And let's be clear, your data is *not* safe with qcow2. So I don't
>> consider this to be a show stopping issue.
>>
>
> I beg your pardon? The one format that was recommended for quite a long
> time now is considered unsafe?
>
Let me be abundantly clear here. qcow2 has never been the "recommended"
format IMHO. When it was introduced, it was introduced as
experimental. This is why block-qcow2.c was forked instead of qcow2
support being integrated into block-qcow.c. There's a ton of duplicate
code between the two. The plan was to eventually merge the two once
qcow2 stabilized. That's not happened. The code was never improved
much since it's introduction until recently.
I have concerns about the fundamental design of qcow2. I believe it
will be difficult to make it safe while having acceptable performance.
There has been some work recently by Gleb Natapov to reduce the
corruption window in qcow2 but it's still there.
I can only recommend qcow2 to casual users. It should *not* be used in
production environments. It pains me to say that because we don't have
a good alternative but there's no way I could recommend its use.
In particular, Jamie's patch reverts one set of patches that reduces the
corruption window to "fix" a corruption bug that is now being
experience. However, since we don't know exactly what the cause of the
new bug is, it's not necessarily true that the revert fixes the bug. It
may just make it more difficult to expose.
There's really no winning scenario here except finding the root cause of
the new bug and fixing it. That still won't make qcow2 safe for
production data though. So as far as I'm concerned, until qcow2 is made
completely safe, it's still an experimental feature.
Regards,
Anthony Liguori
> That would not have happened with Fabrice in charge,
> Dscho
>
>
next prev parent reply other threads:[~2009-02-16 1:20 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 20:48 [Qemu-devel] Cutting a new QEMU release Anthony Liguori
2009-02-03 20:58 ` Glauber Costa
2009-02-03 21:35 ` Laurent Desnogues
2009-02-03 21:50 ` Anthony Liguori
2009-02-03 22:05 ` Laurent Desnogues
2009-02-03 22:47 ` Anthony Liguori
2009-02-03 23:48 ` Glauber Costa
2009-02-04 13:09 ` Ulrich Hecht
2009-02-04 0:31 ` David Turner
[not found] ` <74222928-D24B-4780-BDB0-D537A83C4F68@hotmail.com>
2009-02-04 5:08 ` C.W. Betts
2009-02-03 21:48 ` Rick Vernam
2009-02-03 22:07 ` Daniel P. Berrange
2009-02-04 14:50 ` Aurelien Jarno
2009-02-04 15:23 ` Tristan Gingold
2009-02-04 15:43 ` Lennart Sorensen
2009-02-04 16:01 ` Tristan Gingold
2009-02-04 18:17 ` [Qemu-devel] " Consul
2009-02-04 17:39 ` [Qemu-devel] " Blue Swirl
2009-02-04 17:50 ` Jonathan Kalbfeld
2009-02-04 20:07 ` Blue Swirl
2009-02-07 14:15 ` Stuart Brady
2009-02-04 15:58 ` Glauber Costa
2009-02-07 15:29 ` Shin-ichiro KAWASAKI
2009-02-11 21:49 ` Rob Landley
2009-02-12 14:44 ` Shin-ichiro KAWASAKI
2009-02-12 21:08 ` Rob Landley
2009-02-12 21:44 ` Rob Landley
2009-02-09 12:43 ` Mark McLoughlin
2009-02-09 21:36 ` Anthony Liguori
2009-02-10 0:47 ` Rob Landley
2009-02-10 7:22 ` M. Warner Losh
2009-02-13 8:40 ` Riku Voipio
2009-02-13 9:59 ` Stefano Stabellini
2009-02-13 16:30 ` Jamie Lokier
2009-02-13 17:00 ` Anthony Liguori
2009-02-13 19:04 ` [Qemu-devel] [PATCH] Revert block-qcow2.c to kvm-72 version due to corruption reports Jamie Lokier
2009-02-14 22:23 ` Dor Laor
2009-02-15 2:20 ` Jamie Lokier
2009-02-14 23:13 ` Anthony Liguori
2009-02-15 2:01 ` Jamie Lokier
2009-02-15 4:09 ` Anthony Liguori
2009-02-15 15:42 ` Jamie Lokier
2009-02-15 18:19 ` Anthony Liguori
2009-02-15 18:34 ` Johannes Schindelin
2009-02-16 1:01 ` Anthony Liguori
2009-02-17 0:52 ` Jamie Lokier
2009-02-17 2:55 ` Anthony Liguori
2009-02-16 1:19 ` Anthony Liguori [this message]
2009-02-17 1:01 ` Jamie Lokier
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=4998BF38.3070605@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Johannes.Schindelin@gmx.de \
--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).