xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: Gedalya <gedalya@gedalya.net>,
	xen-devel <xen-devel@lists.xensource.com>,
	637234@bugs.debian.org
Subject: Re: Re: Bug#637234: linux-image-3.0.0-1-686-pae: I/O errors using ext4 under xen
Date: Fri, 26 Aug 2011 13:53:17 -0400	[thread overview]
Message-ID: <20110826175317.GA5043@dumpdata.com> (raw)
In-Reply-To: <1314254828.17978.720.camel@dagon.hellion.org.uk>

On Thu, Aug 25, 2011 at 07:47:08AM +0100, Ian Campbell wrote:
> Hi Konrad,
> 
> Does this look at all familiar? There is some more info in the full bug
> log at http://bugs.debian.org/637234 . In particular, contrary to the
> message below, the user subsequently confirmed that the issue appears to
> be Xen specific (doesn't happen on native or vmware) and that it arose
> between 2.6.39-2-686-pae and 3.0.0-1-686-pae.
> 
> Could it be related to edf6ef59ec7e "xen-blkfront: Introduce
> BLKIF_OP_FLUSH_DISKCACHE support"? That looks like the only pertinent
> change between 2.6.39 and 3.0.


It shouldn't - from the look of it:
[    0.529412] blkfront: xvdc: barrier: enabled

it looks as if the 'feature-barrier' is used. Not 'feature-flush-cache' -
otherwise you would have seen a message about that.

But then.. 3.0 (and 2.6.39) don't do barriers anymore. However the backend
seems to do it. And from my understanding is that the barrier request
is a superset of a flush request so it should work. Put maybe that is
an incorrect assumption.

One way to make sure that is not the case is to disable barriers in the
guest. Meaning in /etc/fstab have something like this:

/dev/xvdc /blah     ext4    errors=remount-ro,barrier=0 0 1


The other question is what version of Dom0 are you running? Is it 2.6.32?
2.6.39?

  parent reply	other threads:[~2011-08-26 17:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110809180728.2279.11548.reportbug@mail1.gedalya.net>
2011-08-25  6:47 ` Bug#637234: linux-image-3.0.0-1-686-pae: I/O errors using ext4 under xen Ian Campbell
2011-08-25  7:20   ` Gedalya
2011-08-26 17:53   ` Konrad Rzeszutek Wilk [this message]
2011-08-26 22:58     ` Gedalya
2011-08-29 14:08       ` Konrad Rzeszutek Wilk
2011-09-07  1:51         ` Bug#637234: [Xen-devel] " Ben Hutchings
2011-09-07 12:29           ` Bug#637234: " Konrad Rzeszutek Wilk

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=20110826175317.GA5043@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=637234@bugs.debian.org \
    --cc=gedalya@gedalya.net \
    --cc=ijc@hellion.org.uk \
    --cc=xen-devel@lists.xensource.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).