From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Linux 3.1 domU + ext3 = WARNING: at fs/ext3/inode.c Date: Thu, 27 Oct 2011 11:41:59 -0400 Message-ID: <20111027154159.GB2909@phenom.dumpdata.com> References: <4EA71270.2050303@theshore.net> <20111025201239.GA13747@phenom.dumpdata.com> <20111025211512.GA2561@phenom.dumpdata.com> <4EA86D00.1080906@theshore.net> <20111026203652.GA10737@phenom.dumpdata.com> <4EA87A5C.6060100@theshore.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4EA87A5C.6060100@theshore.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Christopher S. Aker" Cc: xen devel List-Id: xen-devel@lists.xenproject.org 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?