From: "andrzej zaborowski" <balrog@zabor.org>
To: Jens Axboe <qemu@kernel.dk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC][PATCH] make sure disk writes actually hit disk
Date: Mon, 31 Jul 2006 19:50:41 +0200 [thread overview]
Message-ID: <fb249edb0607311050l42df1ba3kd35c2f2c87330ba1@mail.gmail.com> (raw)
In-Reply-To: <20060731101710.GQ14748@suse.de>
On 31/07/06, Jens Axboe <qemu@kernel.dk> wrote:
> On Mon, Jul 31 2006, andrzej zaborowski wrote:
> > On 30/07/06, Jamie Lokier <jamie@shareable.org> wrote:
> > >Rik van Riel wrote:
> > >> This may look like hair splitting, but so far I've lost a
> > >> (test) postgresql database to this 3 times already. Not getting
> > >> the guest application's data to disk when the application calls
> > >> fsync is a recipe for disaster.
> > >
> > >Exactly the same thing happens with real IDE disks if IDE write
> > >caching (on the drive itself) is enabled, which it is by default. It
> > >is rarer, but it happens.
> >
> > The little difference with QEMU is that there are two caches above it:
> > the host OS'es software cache and the IDE hardware cache. When a guest
> > OS flushes its own software cache its precious data goes to the host's
> > software cache while the guest thinks it's already the IDE cache. This
> > is ofcourse of less importance because data in both caches (hard- and
> > software) is lost when the power is cut off.
>
> But the drive cache does not let the dirty data linger for as long as
> wht OS page/buffer cache.
I would say this an argument speaking for actually using O_SYNC.
>
> > IMHO what really makes IO unreliable in QEMU is that IO errors on the
> > host are not reported to the guest by the IDE emulation and there's an
> > exact place in hw/ide.c where they are arrogantly ignored.
>
> Send a patch, I'm pretty sure nobody would disagree :-)
Here's what I proposed:
http://lists.gnu.org/archive/html/qemu-devel/2005-12/msg00275.html but
I'm afraid it's not correct :P
>
> --
> Jens Axboe
>
>
--
balrog 2oo6
Dear Outlook users: Please remove me from your address books
http://www.newsforge.com/article.pl?sid=03/08/21/143258
next prev parent reply other threads:[~2006-07-31 17:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 19:54 [Qemu-devel] [RFC][PATCH] make sure disk writes actually hit disk Rik van Riel
2006-07-28 19:58 ` [Qemu-devel] " Rik van Riel
2006-07-28 20:12 ` Anthony Liguori
2006-07-28 20:18 ` Rik van Riel
2006-07-28 20:30 ` Paul Brook
2006-07-28 20:43 ` Rik van Riel
2006-07-28 21:01 ` Paul Brook
2006-07-31 7:08 ` Jens Axboe
2006-07-29 9:57 ` [Qemu-devel] " Fabrice Bellard
2006-07-29 14:59 ` Rik van Riel
2006-07-29 16:04 ` Paul Brook
2006-07-29 16:22 ` Rik van Riel
2006-07-29 16:31 ` Paul Brook
2006-07-31 7:08 ` Jens Axboe
2006-07-29 17:33 ` Bill C. Riemers
2006-07-30 21:47 ` Jamie Lokier
2006-07-30 21:41 ` Jamie Lokier
2006-07-31 9:52 ` andrzej zaborowski
2006-07-31 10:17 ` Jens Axboe
2006-07-31 17:50 ` andrzej zaborowski [this message]
2006-07-31 7:08 ` Jens Axboe
2006-07-31 7:56 ` Jonas Maebe
2006-07-31 8:18 ` Jens Axboe
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=fb249edb0607311050l42df1ba3kd35c2f2c87330ba1@mail.gmail.com \
--to=balrog@zabor.org \
--cc=balrogg@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu@kernel.dk \
/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).