From: Avi Kivity <avi@redhat.com>
To: Thomas Mueller <thomas@chaschperli.ch>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH][RFC] Use writeback caching by default with qcow2
Date: Thu, 20 Nov 2008 11:55:15 +0200 [thread overview]
Message-ID: <49253403.6060603@redhat.com> (raw)
In-Reply-To: <gg325v$mfc$1@ger.gmane.org>
Thomas Mueller wrote:
>> Right now, qcow2 isn't a
>> reliable format regardless of the type of cache your using because
>> metadata is not updated in the correct order.
>>
>
> so you don't advise to use qcow2 as a VBD or what do you mean with "isn't
> reliable"?
>
Right, qcow2 is both very slow with cache=writethrough (or off), and may
corrupt itself if the host crashes at the wrong moment.
> or contrawise: on the other formats the metadata is updated in the
> correct order?
>
raw is the only format we're sure of.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
prev parent reply other threads:[~2008-11-20 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 20:24 [Qemu-devel] [PATCH][RFC] Use writeback caching by default with qcow2 Anthony Liguori
2008-11-19 22:27 ` Stefan Berger
[not found] ` <gg325v$mfc$1@ger.gmane.org>
2008-11-20 9:55 ` Avi Kivity [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=49253403.6060603@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=thomas@chaschperli.ch \
/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).