From: David Chatterton <chatz@melbourne.sgi.com>
To: Andrew Elwell <andrewe@epcc.ed.ac.uk>
Cc: linux-xfs@oss.sgi.com, maciej@epcc.ed.ac.uk
Subject: Re: oops with CentOS 4.3 / xfs / nfsd
Date: Tue, 18 Jul 2006 21:03:59 +1000 [thread overview]
Message-ID: <44BCC01F.2020802@melbourne.sgi.com> (raw)
In-Reply-To: <1153214961.6793.15.camel@x41ade>
Andrew,
I may be completely wrong, but the error message suggests to me that you
are exceeding the 4KB stack.
If you can see an archive of this list, also see Nathan's reply to
"Bad page state in process 'nfsd' with xfs", but i'm not sure which
2.6 kernel he is referring to where our stack usage was reduced.
David
Andrew Elwell wrote:
> Hi Folks,
>
> We've migrated some of our storage servers to CentOS 4.3 and are seeing
> lockups. It *could* be hardware I know, and I'm scheduling downtime to
> run memtest86+ ASAP.
>
> Overview:
> 2* LPFC HBA's connecting to our SAN,
> dm setup for multipath to see 4*1.6TB trays
> each tray as a PV in lvm2 sanvg
> xfs on a 3T lv
> NFS exported out as /export/work
>
> using the 2.6.9-34 centosplus SMP kernel (3GHz P4 with hyperthreading
> enabled)
>
> what we normally (~once a day) is simply
>
> do_IRQ: stack overflow: 416
> [<c0107a27>]
>
> on the console and nothing else. (needs a cold reboot)
>
> Having installed netdump (nice tool btw) we got a different error
> yesterday that looks xfs / nfsd related...
>
> (attached)
>
> any help in progressing this would be much appreciated -
>
> Andrew
>
next prev parent reply other threads:[~2006-07-18 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 9:29 oops with CentOS 4.3 / xfs / nfsd Andrew Elwell
2006-07-18 11:03 ` David Chatterton [this message]
2006-07-18 11:36 ` Joshua Baker-LePain
2006-07-18 22:30 ` Nathan Scott
2006-07-19 7:37 ` Andrew Elwell
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=44BCC01F.2020802@melbourne.sgi.com \
--to=chatz@melbourne.sgi.com \
--cc=andrewe@epcc.ed.ac.uk \
--cc=linux-xfs@oss.sgi.com \
--cc=maciej@epcc.ed.ac.uk \
/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