From: Nathan Scott <nathans@sgi.com>
To: Goran Gajic <ggajic@sbb.co.yu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: XFS and 2.6.12-rc5
Date: Fri, 3 Jun 2005 14:41:38 +1000 [thread overview]
Message-ID: <20050603044138.GB1653@frodo> (raw)
In-Reply-To: <Pine.BSF.4.62.0506011308530.86037@mail.sbb.co.yu>
On Wed, Jun 01, 2005 at 01:10:47PM +0200, Goran Gajic wrote:
> xfs partition is exported via nfs to FreeBSD-5.4 machine. This is what I
> find every morning in my syslog:
>
> ------------[ cut here ]------------
> kernel BUG at fs/xfs/support/debug.c:106!
> ...
> [<c0269758>] xfs_bmap_search_extents+0x108/0x140
> [<c026accd>] xfs_bmapi+0x28d/0x1660
There should be some diagnostic text just above this panic message,
what does it say? At a guess, I'd say you have a corrupt inode on
disk, and your nightly cron jobs are tripping this up each time.
The panic happens cos the kernel detects an inode with an extent
map which claiming to have an extent starting at the offset of the
primary superblock. I've seen another case of this recently which
looked like a possible compiler bug, so could you send me both the
full diagnostic message and your compiler version number?
Also, the diagnostic will contain an inode number - for bonus points
run "xfs_db -r -c 'inode XXX' -c print /dev/foo" and send me that as
well. Thanks!
cheers.
--
Nathan
next prev parent reply other threads:[~2005-06-03 4:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 11:10 XFS and 2.6.12-rc5 Goran Gajic
2005-06-03 4:41 ` Nathan Scott [this message]
2005-06-03 8:56 ` Goran Gajic
2005-06-06 4:32 ` Nathan Scott
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=20050603044138.GB1653@frodo \
--to=nathans@sgi.com \
--cc=ggajic@sbb.co.yu \
--cc=linux-kernel@vger.kernel.org \
/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.