From: Badari Pulavarty <pbadari@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: wli@holomorphy.com, linux-fsdevel@vger.kernel.org,
ext2-devel <ext2-devel@lists.sourceforge.net>
Subject: Re: Bufferheads & page-cache reference
Date: 15 Feb 2005 08:03:17 -0800 [thread overview]
Message-ID: <1108483396.20053.1379.camel@dyn318077bld.beaverton.ibm.com> (raw)
In-Reply-To: <20050214185733.7ef3a613.akpm@osdl.org>
On Mon, 2005-02-14 at 18:57, Andrew Morton wrote:
> Badari Pulavarty <pbadari@us.ibm.com> wrote:
> >
> > Most of DB2 customers use filesystem for their database. Under the load,
> > they complain that entire memory in the system is used by filesystem
> > pagecache, freememory is very low and system starts swapping crazy OR
> > see lots of memory allocation failures and OOM killer kills db2.
> > slabinfo shows lots of bufferheads and VM folks claim that, bufferheads
> > are holding a ref. on the pages, so they can't use them. So, I want
> > to find the truth in the story and findout what exactly happening here
> > and which one to blame (VM or FS or IO problems) ?
> >
> > BTW, all these on 2.4 kernels and I don't have a reproducible testcase
> > :(
> >
> > Feb 7 05:35:17 nmcopsu41 kernel: ENOMEM in do_get_write_access,
> > retrying.
>
> Do these machines have a large amount of highmem?
>
> If so, yes, you can oom because lots of highmem pages have buffer_heads
> attached and you've run out of lowmem. The 2.4 VM will go off looking for
> lowmem pages to reclaim and will ignore the highmem pages because there's
> no highmem shortage. Consequently those buffer_heads don't get freed up
> and we're unable to reclaim any lowmem -> oom.
>
> Andrea did a patch along time ago (it'll be in suse 2.4 kernels) which,
> under these circumstances, strip the buffers from those highmem pages when
> they're encountered on the LRU. From a quick read it seems that that patch
> is not in current 2.4 kernels.
>
> It's harder to do that in 2.6 because we have a separate LR per zone.
Our DB2 folks *claims* to have seen this problem both on ia32 and AMD64
customers. So, I am not sure if its really only highmem related. Only
workaround seems to be configure DB2 to not to use more than 1.5GB on a
8GB RAM system :(
I have nothing much to go on, other than looking data from a sick
machine. What should I be looking at, to narrow down the problem
some more ?
BTW, none of these BIG customers will take a patch to figure out
whats happening (since its on their production system) :(
Thanks,
Badari
next prev parent reply other threads:[~2005-02-15 16:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-14 19:30 Bufferheads & page-cache reference Badari Pulavarty
2005-02-14 19:31 ` [Ext2-devel] " Sonny Rao
2005-02-14 21:40 ` Andrew Morton
2005-02-14 22:10 ` William Lee Irwin III
2005-02-14 22:31 ` Andrew Morton
2005-02-14 22:50 ` William Lee Irwin III
2005-02-15 0:22 ` Badari Pulavarty
2005-02-15 2:57 ` Andrew Morton
2005-02-15 16:03 ` Badari Pulavarty [this message]
2005-02-15 17:26 ` Andrew Morton
2005-02-15 1:27 ` Badari Pulavarty
2005-02-15 3:05 ` Andrew Morton
2005-02-15 16:46 ` Badari Pulavarty
2005-02-15 17:54 ` Andrew Morton
2005-02-15 18:15 ` Badari Pulavarty
2005-02-15 19:07 ` Nikita Danilov
2005-02-15 19:39 ` Badari Pulavarty
2005-02-15 20:00 ` Andrew Morton
2005-02-16 0:02 ` [RFC] [PATCH] Generic mpage_writepage() support Badari Pulavarty
2005-02-16 11:41 ` Nikita Danilov
2005-02-16 18:37 ` Badari Pulavarty
2005-02-16 19:09 ` Dave Kleikamp
2005-02-16 19:28 ` Badari Pulavarty
2005-02-16 19:43 ` Dave Kleikamp
2005-02-16 21:38 ` [Ext2-devel] " Badari Pulavarty
2005-02-16 21:46 ` Dave Kleikamp
2005-02-17 0:13 ` [RFC] [PATCH] nobh_write_page() support Badari Pulavarty
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=1108483396.20053.1379.camel@dyn318077bld.beaverton.ibm.com \
--to=pbadari@us.ibm.com \
--cc=akpm@osdl.org \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=wli@holomorphy.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;
as well as URLs for NNTP newsgroup(s).