From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id q9JLq873063139 for ; Fri, 19 Oct 2012 16:52:08 -0500 Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net [150.101.137.141]) by cuda.sgi.com with ESMTP id h3MzAgkSXSq0Bnaq for ; Fri, 19 Oct 2012 14:53:46 -0700 (PDT) Received: from dave by dastard with local (Exim 4.76) (envelope-from ) id 1TPKVj-0006lr-LK for xfs@oss.sgi.com; Sat, 20 Oct 2012 08:53:43 +1100 Date: Sat, 20 Oct 2012 08:53:43 +1100 From: Dave Chinner Subject: Re: xfstests 250 fail on newer kernels Message-ID: <20121019215343.GX2739@dastard> References: <20121019173730.GA23018@andromeda.usersys.redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20121019173730.GA23018@andromeda.usersys.redhat.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: xfs@oss.sgi.com On Fri, Oct 19, 2012 at 02:37:30PM -0300, Carlos Maiolino wrote: > Hi, > > reviewing a patch to xfstests250, I ran it against newer kernels (3.6.0+ and > 3.7.0-rc1) and noticed it is failing. i.e. btree is getting corrupted. It's been failing on mainline kernels for a long time. In fact, i think it's been failing since it was created. But it's not failing due to btree corruption - it's failing because mkfs is not leaving enough space in the AG that contains the log for sanity checks to pass. i.e. that there are always a minimum of 4 blocks of freespace in an AG. This is not actually a problem - the log takes the entire AG, so allocation will never occur in it, so having less than 4 blocks of free space in the AG is just noise in this case. It's never bubbled to the top of my list to fix... > I'm going to take a look at it, but let me know if anybody has already > found/fixed it. If it is failing the check_scratch_fs stage, then it is most likely the above issue. The corrupted btree problem that the test was writen for caused the system to ASSERT fail or crash - i.e. it didn't even run to the point of checking the fs.... Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs