From: Ric Wheeler <rwheeler@redhat.com>
To: Michal Novotny <minovotn@redhat.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] extend e2fsprogs functionality to add EXT2_FLAG_DIRECT option
Date: Tue, 12 Jan 2010 15:01:11 -0500 [thread overview]
Message-ID: <4B4CD507.9010301@redhat.com> (raw)
In-Reply-To: <4B4C9940.8060004@redhat.com>
Just for completeness, this is what we think we have going on:
1) First boot: Running on the host, pygrub reads the device (unmounted)
to bootstrap the guest with image A (kernel + grub.conf)
(2) guest image updates the kernel/grub.conf using weird Xen IO path
(bypassing the host page cache, creating BIO's directly in the host
memory).
Note that at this point in time, the image from (1) is still possibly in
the page cache of the host
(3) reboot of guest - host pygrub uses page cache (stale pages) when
bootstrapping the guest who occasionally boots into the stale image.
This doesn't happen all of the time - if the pages are dropped before
(3) happens, it won't happen.
Uses O_DIRECT has a side effect of invalidating the page cache while
reading.
Dropping VM caches just for the devices in question would fix this or
(as Christoph mentioned) use kvm which does this more sanely :-)
ric
prev parent reply other threads:[~2010-01-12 20:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 9:36 [PATCH] extend e2fsprogs functionality to add EXT2_FLAG_DIRECT option Michal Novotny
2010-01-11 20:06 ` Ric Wheeler
2010-01-12 10:54 ` Michal Novotny
2010-01-12 11:59 ` Ric Wheeler
2010-01-12 12:15 ` Michal Novotny
2010-01-12 12:23 ` Christoph Hellwig
2010-01-12 12:30 ` Michal Novotny
2010-01-12 12:46 ` Christoph Hellwig
2010-01-12 13:01 ` Michal Novotny
2010-01-12 13:04 ` Ric Wheeler
2010-01-12 13:12 ` Michal Novotny
2010-01-12 13:23 ` Michal Novotny
2010-01-12 13:29 ` Ric Wheeler
2010-01-12 13:33 ` Michal Novotny
2010-01-12 14:33 ` Chris Lee
2010-01-12 14:37 ` Michal Novotny
2010-01-12 16:38 ` Christoph Hellwig
2010-01-12 16:43 ` Michal Novotny
2010-01-12 16:47 ` Christoph Hellwig
2010-01-12 16:51 ` Michal Novotny
2010-01-12 16:50 ` Ric Wheeler
2010-01-12 16:53 ` Michal Novotny
2010-01-12 16:56 ` Eric Sandeen
2010-01-12 16:59 ` Ric Wheeler
2010-01-12 17:00 ` Michal Novotny
2010-01-14 13:46 ` Michal Novotny
2010-01-12 12:47 ` Andreas Dilger
2010-01-12 13:04 ` Michal Novotny
2010-01-12 15:16 ` Eric Sandeen
2010-01-12 15:46 ` Michal Novotny
2010-01-12 20:01 ` Ric Wheeler [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=4B4CD507.9010301@redhat.com \
--to=rwheeler@redhat.com \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=minovotn@redhat.com \
--cc=sandeen@redhat.com \
/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).