xfs
[Top] [All Lists]

Re: xfs regression in linux_2.6.28, "XFS_WANT_CORRUPTED_GOTO at line 332

To: Roland Eggner <edvx1@xxxxxxxxxxxxxxxxxx>
Subject: Re: xfs regression in linux_2.6.28, "XFS_WANT_CORRUPTED_GOTO at line 3327 of file fs/xfs/xfs_btree.c"
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Fri, 16 Jan 2009 09:14:38 +1100
Cc: SGI Project XFS mailing list <xfs@xxxxxxxxxxx>
In-reply-to: <200901150402.39801.edvx1@xxxxxxxxxxxxxxxxxx>
Mail-followup-to: Roland Eggner <edvx1@xxxxxxxxxxxxxxxxxx>, SGI Project XFS mailing list <xfs@xxxxxxxxxxx>
References: <200901150402.39801.edvx1@xxxxxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.18 (2008-05-17)
On Thu, Jan 15, 2009 at 04:02:39AM +0100, Roland Eggner wrote:
> Latest (so far) working linux_2.6.27.9
> linux_2.6.28 seems to introduce a xfs regression:

You mean 2.6.29, don't you (i.e. a current TOT development kernel,
not a stable kernel)?

> $  egrep -i '(Linux|gcc) version|corrupted' /var/log/messages
> Jan 10 14:27:29 roland kernel: Linux version 2.6.28.roland.1 (roland@roland) 
> (gcc version 4.2.3 (Debian 4.2.3-3)) #3 Fri Jan 9 16:51:21 CET 2009
> Jan 11 02:00:14 roland kernel: Linux version 2.6.28-git7.roland.0 
> (roland@roland) (gcc version 4.2.3 (Debian 4.2.3-3)) #1 Sun Jan 11 01:29:14 
> CET 2009
> Jan 11 02:36:56 roland kernel: XFS internal error XFS_WANT_CORRUPTED_GOTO at 
> line 3327 of file fs/xfs/xfs_btree.c.  Caller 0xc02488bc

We have received a few reports of that since 2.6.29-git2 after the
big XFS merge occurred. Can you confirm that you are running a very
recent unstable kernel and not a stable 2.6.28 kernel?

BTW, I note your kernel is tainted (like a couple of other
reports of this problem). Can you tell us what module youare
running that taints the kernel so we can correlate that with
other reports of the problem?

As it is, I'm trying to track down the bug that introduced the
regression. However, the bug is not obvious from reviewing the
change it has been bisected down to, nor have I been able to
reproduce it locally.

This one might take a little while to find, so please be patient
and watch the list for updates.

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>