From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: Re: xfstests 250 fail on newer kernels
Date: Sat, 20 Oct 2012 08:53:43 +1100 [thread overview]
Message-ID: <20121019215343.GX2739@dastard> (raw)
In-Reply-To: <20121019173730.GA23018@andromeda.usersys.redhat.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
next prev parent reply other threads:[~2012-10-19 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 17:37 xfstests 250 fail on newer kernels Carlos Maiolino
2012-10-19 21:53 ` Dave Chinner [this message]
2012-10-20 11:24 ` Carlos Maiolino
2012-10-21 22:31 ` Dave Chinner
2012-10-23 12:24 ` Christoph Hellwig
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=20121019215343.GX2739@dastard \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.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.