From: "J.H." <warthog9@kernel.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: jaxboe@fusionio.com, Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@infradead.org>
Subject: More XFS resource starvation?
Date: Mon, 15 Nov 2010 10:30:38 -0800 [thread overview]
Message-ID: <4CE17C4E.7010206@kernel.org> (raw)
So apparently I'm having fun tripping over all kinds of bugs lately.
I've seen this a couple of times now on the box in question. Usually
happens after a few days, or after particularly heavy rsync traffic on
the box.
http://pastebin.osuosl.org/36014
Christoph seemed to think it's a memory exhaustion problem, so I've
included the /proc/meminfo and as you can see there's plenty of memory
around on the system.
Loads have, expectedly, climbed currently around 1250.05 but growing slowly.
Quick overview of the underlying storage:
xfs -> md (raid 0) -+--> P812 hardware raid6 (cciss driver)
|
+--> P812 hardware raid6 (cciss driver)
This is running on an HP DL380 G7.
I saw this both on an older 2.6.30.10-105.2.23.fc11.x86_64, and
currently on 2.6.34.7-61.fc13.x86_64 (both being Fedora stock kernels)
I have not seen this on a very similar DL380 G6, with the same storage
setup and it is currently running the 2.6.30 kernel from above.
Christoph suggest increasing the nr_request values for each of the
underlying devices, but this didn't seem to change anything
significantly on the system.
Anyone have any ideas on what's going on?
- John 'Warthog9' Hawley
next reply other threads:[~2010-11-15 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 18:30 J.H. [this message]
2010-11-15 19:08 ` More XFS resource starvation? Simon Kirby
2010-11-15 23:49 ` Dave Chinner
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=4CE17C4E.7010206@kernel.org \
--to=warthog9@kernel.org \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.