From: Nathan Scott <nathans@sgi.com>
To: Oliver Kiddle <okiddle@yahoo.co.uk>,
Andrew Morton <akpm@osdl.org>,
hch@infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: page allocation failure
Date: Tue, 20 Jan 2004 17:00:52 +1100 [thread overview]
Message-ID: <20040120060052.GC953@frodo> (raw)
In-Reply-To: <20040119193837.6369d498.akpm@osdl.org>
On Mon, Jan 19, 2004 at 07:38:37PM -0800, Andrew Morton wrote:
> Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
> >
> > It has happened three times now and on all occasions, I was untarring a
> > huge file on an XFS partition. I assume the problem is something to do
> > with VM. The machine has 1GB of RAM which should be plenty. For the
> ...
> You probably should apply this patch to tell us where the allocation
> failures are coming from. Make sure that CONFIG_KALLSYMS is enabled in
> kernel config.
We do have known issues in XFS on 2.6 with handling certain VM
allocation failures -- maybe hitting that here. Christoph has
been looking at making XFS do a better job there; __GFP_NOFAIL
allocations failing seem to be the worst issue for us - on the
occasions I've hit that though, its always immediately fatal.
cheers.
--
Nathan
next prev parent reply other threads:[~2004-01-20 6:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 11:36 page allocation failure Oliver Kiddle
2004-01-19 14:54 ` Mike Fedyk
2004-01-19 17:29 ` Oliver Kiddle
2004-01-19 18:12 ` Mike Fedyk
2004-01-20 3:38 ` Andrew Morton
2004-01-20 6:00 ` Nathan Scott [this message]
2004-01-20 17:08 ` Oliver Kiddle
2004-01-20 18:35 ` Mike Fedyk
2004-01-22 9:29 ` Oliver Kiddle
2004-01-22 9:59 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2004-08-24 20:05 Dominik Karall
2004-08-24 20:05 ` Andrew Morton
2004-08-24 22:57 ` David S. Miller
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=20040120060052.GC953@frodo \
--to=nathans@sgi.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=okiddle@yahoo.co.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