All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>,
	Jacek Luczak <difrost.kernel@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	hch@infradead.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 06:29:10 -0500	[thread overview]
Message-ID: <20090120112910.GA6831@infradead.org> (raw)
In-Reply-To: <20090120004611.GA6445@disturbed>

On Tue, Jan 20, 2009 at 11:46:11AM +1100, Dave Chinner wrote:
> On Mon, Jan 19, 2009 at 12:44:48PM -0600, Eric Sandeen wrote:
> > Jacek Luczak wrote:
> > > Hi All,
> > > 
> > > I've stepped into XFS issue/bug. Yesterday I've compiled 2.6.29-rc2 and no
> > > didn't found errors. Today I've booted my notebook and XFS bug have occurred.
> > > System reboot didn't helped, same error appeared.
> > > 
> > > Some info:
> > > [1] config: http://pin.if.uz.zgora.pl/~difrost/linux-next/2.6.29-rc2.config
> > > [2] kernel logs:
> > > http://pin.if.uz.zgora.pl/~difrost/linux-next/2.6.29-rc2_XFS-bug.log
> > > [3] most interesting part of log below.
> > 
> > so this happens every mount?  Reproducible is good.  How large is the
> > filesystem (too large to extract elsewhere for analysis...?) (plus I
> > suppose it'll be hard to get to it when you can't even boot....)
> 
> XFS folks, I suspect the common link between all the reports of this
> bug is that they are on 32-bit kernels. I can't reproduce this on
> a 64 bit kernel, and I'm trying to get a 32-bit UML built right now
> to test this theory.

I'm doing about half of my testing on 32 bit x86, and I couldn't
reproduce the detailed receipe  in the kernel.org bugzilla yet.

Just curious:  do you have CONFIG_LBD set?

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

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>,
	Jacek Luczak <difrost.kernel@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	hch@infradead.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 06:29:10 -0500	[thread overview]
Message-ID: <20090120112910.GA6831@infradead.org> (raw)
In-Reply-To: <20090120004611.GA6445@disturbed>

On Tue, Jan 20, 2009 at 11:46:11AM +1100, Dave Chinner wrote:
> On Mon, Jan 19, 2009 at 12:44:48PM -0600, Eric Sandeen wrote:
> > Jacek Luczak wrote:
> > > Hi All,
> > > 
> > > I've stepped into XFS issue/bug. Yesterday I've compiled 2.6.29-rc2 and no
> > > didn't found errors. Today I've booted my notebook and XFS bug have occurred.
> > > System reboot didn't helped, same error appeared.
> > > 
> > > Some info:
> > > [1] config: http://pin.if.uz.zgora.pl/~difrost/linux-next/2.6.29-rc2.config
> > > [2] kernel logs:
> > > http://pin.if.uz.zgora.pl/~difrost/linux-next/2.6.29-rc2_XFS-bug.log
> > > [3] most interesting part of log below.
> > 
> > so this happens every mount?  Reproducible is good.  How large is the
> > filesystem (too large to extract elsewhere for analysis...?) (plus I
> > suppose it'll be hard to get to it when you can't even boot....)
> 
> XFS folks, I suspect the common link between all the reports of this
> bug is that they are on 32-bit kernels. I can't reproduce this on
> a 64 bit kernel, and I'm trying to get a 32-bit UML built right now
> to test this theory.

I'm doing about half of my testing on 32 bit x86, and I couldn't
reproduce the detailed receipe  in the kernel.org bugzilla yet.

Just curious:  do you have CONFIG_LBD set?

  parent reply	other threads:[~2009-01-20 11:29 UTC|newest]

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