From: Roman Mamedov <rm@romanrm.ru>
To: Konstantinos Skarlatos <k.skarlatos@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: "md_raid5: page allocation failure" when resyncing on 3.2
Date: Tue, 10 Jan 2012 00:31:07 +0600 [thread overview]
Message-ID: <20120110003107.432e4542@natsu> (raw)
In-Reply-To: <4F0B2303.4080109@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]
On Mon, 09 Jan 2012 19:25:23 +0200
Konstantinos Skarlatos <k.skarlatos@gmail.com> wrote:
> Hello, i got this kernel message when i was resyncing my md raid 5 array
> on a linux 3.2 machine.
This probably doesn't have much to do with md, it is a generic Linux kernel failure in the VM subsystem.
If the search on bugzilla.kernel.org was up, I'd point you to bug numbers (there was quite a lot of reports), but it isn't, so just see:
http://www.google.com/search?ie=UTF-8&q=page+allocation+failure
https://bugzilla.redhat.com/buglist.cgi?quicksearch=page+allocation+failure
e.g.: "they are happening during heavy network and disk activity when the system has plenty of memory free"
https://bugzilla.redhat.com/show_bug.cgi?id=551937
and: "This is very common. e1000 attempts to do large memory allocations from within interrupt context and the page allocator cannot satisfy the allocation and is not allowed to do the necessary work to make the allocation attempt succeed. It's the same with all net drivers"
http://kerneltrap.org/mailarchive/linux-netdev/2009/4/13/5473414
In your backtrace I see the system was also handling a network transfer with the r8169 driver; do you use jumbo frames there (MTU over 1500)?
--
With respect,
Roman
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-01-09 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 17:25 "md_raid5: page allocation failure" when resyncing on 3.2 Konstantinos Skarlatos
2012-01-09 18:31 ` Roman Mamedov [this message]
2012-01-09 22:50 ` Konstantinos Skarlatos
2012-01-10 1:03 ` Mikael Abrahamsson
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=20120110003107.432e4542@natsu \
--to=rm@romanrm.ru \
--cc=k.skarlatos@gmail.com \
--cc=linux-raid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).