From: Andrew Elwell <andrewe@epcc.ed.ac.uk>
To: Nathan Scott <nathans@sgi.com>
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:37:28 +0100 [thread overview]
Message-ID: <20060719073728.GA14530@garnet.epcc.ed.ac.uk> (raw)
In-Reply-To: <20060719083014.B1935136@wobbly.melbourne.sgi.com>
> 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.
More than likely - the filesystem is exported to our Blue Gene rack
so gets hammered by parallel IO constantly. Oh, and the server also
exports a chunk of SATA raid out (3ware controller) as pvfs2...
I guess our priority should be to try and "source" some more memory
than the 512M we have in at the moment.
> Your options are to take
> steps to combat inode extent fragmentation (like fsr), or use a
> more recent kernel (2.6.17+ IIRC).
OK - we were trying to stay reasonably simple by using vendor kernels but I guess it's time for a quick "make menuconfig"
Ta
Andrew
--
Andrew Elwell, System Administrator EPCC
Tel 0131 445 7833 (ACF Building)
Tel 0131 650 5023 (Rm 3309, JCMB)
prev parent reply other threads:[~2006-07-19 8:44 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
2006-07-19 7:37 ` Andrew Elwell [this message]
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=20060719073728.GA14530@garnet.epcc.ed.ac.uk \
--to=andrewe@epcc.ed.ac.uk \
--cc=maciej@epcc.ed.ac.uk \
--cc=nathans@sgi.com \
--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