From: Steve Lord <lord@xfs.org>
To: Joshua Baker-LePain <jlb17@duke.edu>
Cc: Lee Revell <rlrevell@joe-job.com>,
Gregory Brauer <greg@wildbrain.com>,
linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com,
Jakob Oestergaard <jakob@unthought.net>,
Chris Wedgwood <cw@f00f.org>
Subject: Re: kernel OOPS for XFS in xfs_iget_core (using NFS+SMP+MD)
Date: Thu, 19 May 2005 16:29:36 -0500 [thread overview]
Message-ID: <428D0540.4000107@xfs.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0505191713540.7094@chaos.egr.duke.edu>
Joshua Baker-LePain wrote:
> On Thu, 19 May 2005 at 5:09pm, Lee Revell wrote
>
>
>>On Thu, 2005-05-19 at 17:00 -0400, Joshua Baker-LePain wrote:
>>
>>>May 19 16:47:10 norbert kernel: Filesystem "md0": XFS internal error xfs_da_do_buf(1) at line 2176 of file fs/xfs/xfs_da_btree.c. Caller 0xf8c90148
>
> *snip*
>
>>Couldn't this be a stack overflow? That's a very large kernel stack.
>
>
> I am using 8K stacks, and that's all the kernel messages I see.
>
The stack backtrace just converts all the code addresses it sees on
the stack, so you get extra false positives in there, it is not as
large as it seems.
Try setting /proc/sys/fs/xfs/error_level to 1 and running again,
it should spout out some more information about what it thinks
is corrupted.
Does xfs_repair report anything after this has happened, it looks
like it is trying to read a directory block up from disk to satisfy
a lookup request and failing for some reason. My suspicion is that
the filesystem will look ok (unmount it, then remount to reply the
log, then unmount again before running repair).
anything else in the syslog shortly before this?
Steve
next prev parent reply other threads:[~2005-05-19 21:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 20:45 kernel OOPS for XFS in xfs_iget_core (using NFS+SMP+MD) Gregory Brauer
2005-05-14 18:47 ` Chris Wedgwood
2005-05-18 17:38 ` Gregory Brauer
2005-05-18 17:59 ` Chris Wedgwood
2005-05-18 19:52 ` Jakob Oestergaard
2005-05-18 20:00 ` Joshua Baker-LePain
2005-05-18 20:20 ` Jakob Oestergaard
2005-05-18 20:53 ` Gregory Brauer
2005-05-18 20:43 ` Gregory Brauer
2005-05-19 19:43 ` Joshua Baker-LePain
2005-05-19 21:00 ` Joshua Baker-LePain
2005-05-19 21:09 ` Lee Revell
2005-05-19 21:16 ` Joshua Baker-LePain
2005-05-19 21:29 ` Steve Lord [this message]
2005-05-19 21:32 ` Steve Lord
2005-05-19 21:38 ` Joshua Baker-LePain
2005-05-19 21:43 ` Steve Lord
2005-05-19 21:35 ` Chris Wedgwood
2005-05-19 21:27 ` Chris Wedgwood
2005-05-19 21:42 ` Joshua Baker-LePain
2005-05-19 21:48 ` Joshua Baker-LePain
2005-05-19 22:03 ` Gregory Brauer
2005-08-18 18:49 ` kristina clair
2005-08-18 22:58 ` Nathan Scott
2005-08-19 14:59 ` kristina clair
2005-05-19 21:49 ` Lee Revell
2005-05-19 21:52 ` Joshua Baker-LePain
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=428D0540.4000107@xfs.org \
--to=lord@xfs.org \
--cc=cw@f00f.org \
--cc=greg@wildbrain.com \
--cc=jakob@unthought.net \
--cc=jlb17@duke.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=rlrevell@joe-job.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