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: Wed, 26 Oct 2011 16:36:52 -0400 Message-ID: <20111026203652.GA10737@phenom.dumpdata.com> References: <4EA71270.2050303@theshore.net> <20111025201239.GA13747@phenom.dumpdata.com> <20111025211512.GA2561@phenom.dumpdata.com> <4EA86D00.1080906@theshore.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4EA86D00.1080906@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 04:26:40PM -0400, Christopher S. Aker wrote: > On 10/25/11 5:15 PM, Konrad Rzeszutek Wilk wrote: > >You see the same exact thing with 3.0.6? > > It works with 3.0.4 - do you need me to try 3.0.6 specifically? No need. > > >but you said that if you use 3.0 domU with 2.6.18 you do not get the > >type of warnings as above? > > Correct. > > >Also, when the DomU guest starts it should report if it "thinks" it > >supports barriers. Something like: blkbfront: xvda: barrier > > > >Or is this the only message you get from blkfront?? > > 2.6.18 dom0 + 3.0.4 domU produces this and nothing else: > > blkfront: xvda: barrier: enabled > blkfront: xvdb: barrier: enabled > > 2.6.18 dom0 = works with 3.0.4, breaks with 3.1. OK, so there is nothing that changed in 3.0 through 3.1 in xen-blkfront.c. Well, there was a name change, but nothing else. 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.