From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jacek Luczak <difrost.kernel@gmail.com>,
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: Wed, 21 Jan 2009 00:35:21 +1100 [thread overview]
Message-ID: <20090120133521.GD10158@disturbed> (raw)
In-Reply-To: <20090120114906.GA12526@infradead.org>
On Tue, Jan 20, 2009 at 06:49:06AM -0500, Christoph Hellwig wrote:
> On Tue, Jan 20, 2009 at 12:47:16PM +0100, Jacek Luczak wrote:
> > Christoph Hellwig pisze:
> > > 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?
> >
> > the answer is:
> > $ grep LBD .config
> > # CONFIG_LBD is not set
>
> Ok, let me reproduce it without that set..
Good call, Christoph. I have a reproduce on ia32, CONFIG_LBD=n,
1k block size, 16 AGs in 4GB. Filesystem pre-prepared by
copying a build kernel onto it then 'make mrproper' to put
holes in it. Then, on boot:
dave@xfs-32:/mnt$ sudo mount /dev/sdb /mnt; cd /mnt
dave@xfs-32:/mnt$ cp /home/dave/linux-2.6.tar.gz . ; sync
dave@xfs-32:/mnt$ sudo xfs_bmap -v linux-2.6.tar.gz
linux-2.6.tar.gz:
EXT: FILE-OFFSET BLOCK-RANGE AG AG-OFFSET TOTAL
0: [0..150271]: 92112..242383 0 (92112..242383) 150272
1: [150272..346879]: 256188..452795 0 (256188..452795) 196608
2: [346880..445183]: 906390..1004693 1 (382102..480405) 98304
3: [445184..494335]: 770022..819173 1 (245734..294885) 49152
4: [494336..543487]: 720870..770021 1 (196582..245733) 49152
5: [543488..592639]: 671718..720869 1 (147430..196581) 49152
6: [592640..641791]: 622566..671717 1 (98278..147429) 49152
7: [641792..737023]: 1398498..1493729 2 (349922..445153) 95232
8: [737024..781055]: 1353872..1397903 2 (305296..349327) 44032
9: [781056..830207]: 1304720..1353871 2 (256144..305295) 49152
10: [830208..879359]: 1255566..1304717 2 (206990..256141) 49152
11: [879360..925367]: 1209558..1255565 2 (160982..206989) 46008
dave@xfs-32:/mnt$ > linux-2.6.tar.gz
Connection to xfs-32 closed.
I'll see if this is reproducable, and if it is I'll start
instrumenting in the morning during the LCA keynote. ;)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2009-01-20 13:35 UTC|newest]
Thread overview: 22+ 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-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
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 [this message]
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=20090120133521.GD10158@disturbed \
--to=david@fromorbit.com \
--cc=difrost.kernel@gmail.com \
--cc=hch@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).