From: Eric Sandeen <sandeen@sandeen.net>
To: David Dougall <davidd@et.byu.edu>
Cc: nfs@lists.sourceforge.net, xfs@oss.sgi.com
Subject: Re: kernel panic after upgrading to 2.6
Date: Tue, 24 Oct 2006 12:11:43 -0500 [thread overview]
Message-ID: <453E494F.8080808@sandeen.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0610240938400.8370@lewis.et.byu.edu>
David Dougall wrote:
> I am running kernel 2.6.18 after trying 2.6.17.6 and 2.6.17.13 with
> similar results. I continue to have nfs servers kernel panic on a very
> regular basis, every few days. Sometimes I need to do an xfs_repair to
> get the filesystem to remount. I got the following kernel panic message
> from the syslog this time:
> Message from syslogd@nfs09 at Tue Oct 24 09:35:14 2006 ...
> nfs09 kernel: Oops: 0000 [#1]
If you ran 2.6.17 < 2.6.17.7, there was a bug:
http://oss.sgi.com/projects/xfs/faq.html#dir2
I would suggest getting xfsprogs v. 2.8.10 or newer, as referenced in
the faq, repair your filesystem, and see if the problem is resolved.
-Eric
next prev parent reply other threads:[~2006-10-24 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 15:48 kernel panic after upgrading to 2.6 David Dougall
2006-10-24 17:11 ` Eric Sandeen [this message]
2006-10-24 17:14 ` David Dougall
2006-10-24 19:03 ` David Dougall
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=453E494F.8080808@sandeen.net \
--to=sandeen@sandeen.net \
--cc=davidd@et.byu.edu \
--cc=nfs@lists.sourceforge.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