From: Dave Chinner <david@fromorbit.com>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
Tim Shimmin <xfs-masters@oss.sgi.com>,
xfs@oss.sgi.com, linux-kernel@vger.kernel.org,
Johannes Weiner <hannes@saeurebad.de>
Subject: Re: latest -git: kernel BUG at fs/xfs/support/debug.c:54!
Date: Fri, 18 Jul 2008 08:40:12 +1000 [thread overview]
Message-ID: <20080717224012.GH29319@disturbed> (raw)
In-Reply-To: <19f34abd0807171229p724cc44ese3cb064a65fbd2c0@mail.gmail.com>
On Thu, Jul 17, 2008 at 09:29:39PM +0200, Vegard Nossum wrote:
> On Thu, Jul 17, 2008 at 9:18 PM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
> > Thanks, you are right. I have adjusted my configuration, but I am
> > still able to produce this:
> >
> > BUG: unable to handle kernel paging request at b62a66e0
> > IP: [<c030ef88>] xfs_alloc_fix_freelist+0x28/0x490
>
> FWIW, this is fs/xfs/xfs_alloc.c:1817:
>
> if (!pag->pagf_init) {
Which kind of implies that we've got a bogus fsbno
that we're using as the basis of allocation.....
What is the corruption you are inducing? Can you produce
a xfs_metadump image of the filesystem and put it up somewhere
that we can access it?
I suspect that we are not validating the block numbers coming
out of the various btrees as landing inside the filesystem....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-07-17 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 17:46 latest -git: kernel BUG at fs/xfs/support/debug.c:54! Vegard Nossum
2008-07-17 19:05 ` Eric Sandeen
2008-07-17 19:18 ` Vegard Nossum
2008-07-17 19:29 ` Vegard Nossum
2008-07-17 22:40 ` Dave Chinner [this message]
2008-07-19 13:16 ` Vegard Nossum
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=20080717224012.GH29319@disturbed \
--to=david@fromorbit.com \
--cc=hannes@saeurebad.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=vegard.nossum@gmail.com \
--cc=xfs-masters@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox