From: Kevin Wolf <kwolf@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qcow2: make cache=unsafe usable
Date: Wed, 07 Sep 2011 11:56:22 +0200 [thread overview]
Message-ID: <4E673FC6.60007@redhat.com> (raw)
In-Reply-To: <1315387463-14623-1-git-send-email-avi@redhat.com>
Am 07.09.2011 11:24, schrieb Avi Kivity:
> Currently cache=unsafe is unsafe to the point of unusability - the
> caches are never written to disk except on exit so anything except
> an orderly exit -- including live migration -- leaves the disk image
> corrupted.
>
> Fix by interpreting flush requests and doing everything except flushing
> the underlying file. The contents of the metadata cache are transferred
> to the host pagecache, so that qemu aborts keep the disk in a consistent
> state, and live migration (on the same host, or if using a coherent
> filesystem) works.
>
> Signed-off-by: Avi Kivity <avi@redhat.com>
> ---
>
> Untested - is this the right approach?
Hm, could work, even though I don't like it very much. The alternative
approach would be something like this (not only untested, but won't even
compile):
diff --git a/block.c b/block.c
index a8c789a..1aa5967 100644
--- a/block.c
+++ b/block.c
@@ -1723,10 +1723,6 @@ const char *bdrv_get_device_name(BlockDriverState
*bs)
int bdrv_flush(BlockDriverState *bs)
{
- if (bs->open_flags & BDRV_O_NO_FLUSH) {
- return 0;
- }
-
if (bs->drv && bdrv_has_async_flush(bs->drv) && qemu_in_coroutine()) {
return bdrv_co_flush_em(bs);
}
@@ -2624,10 +2620,6 @@ BlockDriverAIOCB *bdrv_aio_flush(BlockDriverState
*bs,
trace_bdrv_aio_flush(bs, opaque);
- if (bs->open_flags & BDRV_O_NO_FLUSH) {
- return bdrv_aio_noop_em(bs, cb, opaque);
- }
-
if (!drv)
return NULL;
return drv->bdrv_aio_flush(bs, cb, opaque);
diff --git a/block/raw-posix.c b/block/raw-posix.c
index bcf50b2..bb0c0c5 100644
--- a/block/raw-posix.c
+++ b/block/raw-posix.c
@@ -629,6 +629,10 @@ static BlockDriverAIOCB
*raw_aio_flush(BlockDriverState *bs,
{
BDRVRawState *s = bs->opaque;
+ if (bs->open_flags & BDRV_O_NO_FLUSH) {
+ return bdrv_aio_noop_em(bs, cb, opaque);
+ }
+
if (fd_open(bs) < 0)
return NULL;
@@ -839,6 +843,11 @@ static int raw_create(const char *filename,
QEMUOptionParameter *options)
static int raw_flush(BlockDriverState *bs)
{
BDRVRawState *s = bs->opaque;
+
+ if (bs->open_flags & BDRV_O_NO_FLUSH) {
+ return 0;
+ }
+
return qemu_fdatasync(s->fd);
}
next prev parent reply other threads:[~2011-09-07 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 9:24 [Qemu-devel] [PATCH] qcow2: make cache=unsafe usable Avi Kivity
2011-09-07 9:47 ` Alexander Graf
2011-09-07 9:56 ` Kevin Wolf [this message]
2011-09-07 10:07 ` Avi Kivity
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=4E673FC6.60007@redhat.com \
--to=kwolf@redhat.com \
--cc=avi@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).