Re: Linux 3.1 domU + ext3 = WARNING: at fs/ext3/inode.c

[Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>]

On Thu, Oct 27, 2011 at 07:23:28PM +0300, Pasi Kärkkäinen wrote:
> On Thu, Oct 27, 2011 at 11:41:59AM -0400, Konrad Rzeszutek Wilk wrote:
> > 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?
> > 
> 
> Could it be?:
> http://kernelnewbies.org/Linux_3.1#head-12eb55d046763d8b789ff44c50b96c41b203d65e
> 
> "Filesystem barriers enabled by default in Ext3"

Oh, <smacks his head>

I hadn't realized this was a patch - thought it was some CONFIG option to turn it on.

So Christopher if this:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=00eacd66cd8ab5fff9df49aa3f261ad43d495434

is reverted do you get the problems?