public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jacek Luczak <difrost.kernel@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Eric Sandeen <sandeen@sandeen.net>,
	LKML <linux-kernel@vger.kernel.org>,
	xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [XFS] 2.6.29-rc2: XFS internal error XFS_WANT_CORRUPTED_GOTO
Date: Tue, 20 Jan 2009 07:45:15 -0500	[thread overview]
Message-ID: <20090120124515.GA31838@infradead.org> (raw)
In-Reply-To: <20090120121335.GA19182@infradead.org>

On Tue, Jan 20, 2009 at 07:13:35AM -0500, Christoph Hellwig wrote:
> On Tue, Jan 20, 2009 at 06:49:06AM -0500, Christoph Hellwig wrote:
> > > > Just curious:  do you have CONFIG_LBD set?
> > > > 
> > > Hi Christoph,
> > > 
> > > the answer is:
> > > $ grep LBD .config
> > > # CONFIG_LBD is not set
> > 
> > Ok, let me reproduce it without that set..
> 
> Ok, on 32-bit x86 without CONFIG_LBD I can reliably reproduce the issue
> with the following script:

Bisected down to:

commit 91cca5df9bc85efdabfa645f51d54259ed09f4bf
Author: Christoph Hellwig <hch@infradead.org>
Date:   Thu Oct 30 16:58:01 2008 +1100

    [XFS] implement generic xfs_btree_delete/delrec

    Make the btree delete code generic. Based on a patch from David Chinner
    with lots of changes to follow the original btree implementations more
    closely. While this loses some of the generic helper routines for
    inserting/moving/removing records it also solves some of the one off bugs
    in the original code and makes it easier to verify.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-01-20 12:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <497468C1.3000001@gmail.com>
2009-01-19 18:44 ` [XFS] 2.6.29-rc2: XFS internal error XFS_WANT_CORRUPTED_GOTO Eric Sandeen
2009-01-20  0:46   ` Dave Chinner
2009-01-20  9:26     ` Jacek Luczak
2009-01-20 11:29     ` Christoph Hellwig
2009-01-20 11:47       ` Jacek Luczak
2009-01-20 11:49         ` Christoph Hellwig
2009-01-20 12:13           ` Christoph Hellwig
2009-01-20 12:45             ` Christoph Hellwig [this message]
2009-01-20 13:58               ` Jacek Luczak
2009-01-20 14:05                 ` Christoph Hellwig
2009-01-20 14:13                   ` Jacek Luczak
2009-01-20 14:23                   ` Jacek Luczak
2009-01-20 14:32                     ` Christoph Hellwig
2009-01-21  4:05                     ` Dave Chinner
2009-01-21  9:04                       ` Jacek Luczak
2009-01-21 22:58                         ` Dave Chinner
2009-01-20 13:35           ` Dave Chinner
2009-01-20 23:03             ` [PATCH] " Dave Chinner
2009-01-20 23:22               ` Christoph Hellwig
2009-01-20  9:24   ` Jacek Luczak
2009-01-20 10:42     ` Jacek Luczak

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=20090120124515.GA31838@infradead.org \
    --to=hch@infradead.org \
    --cc=difrost.kernel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox