From: Nathan Scott <nathans@sgi.com>
To: Andrew Elwell <andrewe@epcc.ed.ac.uk>
Cc: xfs@oss.sgi.com, maciej@epcc.ed.ac.uk
Subject: Re: oops with CentOS 4.3 / xfs / nfsd
Date: Wed, 19 Jul 2006 08:30:14 +1000 [thread overview]
Message-ID: <20060719083014.B1935136@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <1153214961.6793.15.camel@x41ade>; from andrewe@epcc.ed.ac.uk on Tue, Jul 18, 2006 at 10:29:21AM +0100
On Tue, Jul 18, 2006 at 10:29:21AM +0100, 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.
> ...
> IP 172.20.0.224
> SysRq : HELP : loglevel0-8 reBoot Crash tErm kIll saK showMem powerOff showPc unRaw Sync showTasks Unmount shoWcpus
> nfsd: page allocation failure. order:4, mode:0x50
This is very likely to be due to the way older versions of XFS
managed incore inode extent lists. So, you've likely got a very
fragmented file/files here, and XFS used to require large amounts
of contiguous memory to deal with that. Your options are to take
steps to combat inode extent fragmentation (like fsr), or use a
more recent kernel (2.6.17+ IIRC).
Oh yes, and like Joshua said, those old kernels also had 4Kstack
related issues.
cheers.
--
Nathan
next prev parent reply other threads:[~2006-07-18 22:31 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
2006-07-18 11:36 ` Joshua Baker-LePain
2006-07-18 22:30 ` Nathan Scott [this message]
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=20060719083014.B1935136@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=andrewe@epcc.ed.ac.uk \
--cc=maciej@epcc.ed.ac.uk \
--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