From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: xen devel <xen-devel@lists.xensource.com>
Subject: Re: Linux 3.1 domU + ext3 = WARNING: at fs/ext3/inode.c
Date: Thu, 27 Oct 2011 11:41:59 -0400 [thread overview]
Message-ID: <20111027154159.GB2909@phenom.dumpdata.com> (raw)
In-Reply-To: <4EA87A5C.6060100@theshore.net>
On Wed, Oct 26, 2011 at 05:23:40PM -0400, Christopher S. Aker wrote:
> On 10/26/11 4:36 PM, Konrad Rzeszutek Wilk wrote:
> > I am going to bet that if you compile 3.0.4 or 3.0.6 with that
> > fancy new config option that turns EXT3_ORDERED_something you will
> > see the same exact problem.
>
> Switching that back to match my 3.0 config is the first thing I
> tried, with no joy.
>
> I'll reset and try a few more ideas...
OK. I am kind of lost of what made all this happen - there was nothing
between 3.0 and 3.1 in the Xen blkfront code.
Perhaps there is something new and fancy in the Ext3 (or ext4) that is
causing all this mayhem?
next prev parent reply other threads:[~2011-10-27 15:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 19:48 Linux 3.1 domU + ext3 = WARNING: at fs/ext3/inode.c Christopher S. Aker
2011-10-25 20:12 ` Konrad Rzeszutek Wilk
2011-10-25 20:40 ` Christopher S. Aker
2011-10-25 21:01 ` Konrad Rzeszutek Wilk
2011-10-25 21:15 ` Konrad Rzeszutek Wilk
2011-10-26 20:26 ` Christopher S. Aker
2011-10-26 20:36 ` Konrad Rzeszutek Wilk
2011-10-26 21:23 ` Christopher S. Aker
2011-10-27 15:41 ` Konrad Rzeszutek Wilk [this message]
2011-10-27 16:23 ` Pasi Kärkkäinen
2011-10-27 16:41 ` Konrad Rzeszutek Wilk
2011-12-01 19:10 ` 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=20111027154159.GB2909@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=caker@theshore.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.