All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jan-Frode Myklebust <janfrode@parallab.uib.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOM-killer going crazy.
Date: Mon, 26 Jul 2004 21:43:24 +1000	[thread overview]
Message-ID: <4104EE5C.406@yahoo.com.au> (raw)
In-Reply-To: <20040726111032.GA2067@ii.uib.no>

Jan-Frode Myklebust wrote:
> On Mon, Jul 26, 2004 at 08:55:03PM +1000, Nick Piggin wrote:
> 
>>Can you just check you CONFIG_SWAP is on and /proc/sys/vm/laptop_mode is 0,
>>and that you have some swap enabled.
> 
> 
> # grep CONFIG_SWAP .config
> CONFIG_SWAP=y
> # cat /proc/sys/vm/laptop_mode
> 0
> # free
>              total       used       free     shared    buffers     cached
> Mem:       2074708    1223324     851384          0        296     258376
> -/+ buffers/cache:     964652    1110056
> Swap:      2040244          0    2040244
> 

Good. Just making sure.

> 
> 
>>If the problem persists, can you send a copy each of 
>>/proc/sys/fs/dentry-state,
>>/proc/slabinfo and /proc/vmstat before and after you run dsmc until it goes
>>OOM please?
> 
> 
> I turned of a option (MEMORYEFFICIENTBACKUP) in 'dsmc', and then it uses a bit 
> more memory, and crashes quicker.
> 

Thanks. Let's see.

dentry-state before
> 644923  572300  45      0       0       0
after
 > 570734  495922  45      0       0       0

slabinfo before
> # name            <active_objs> <num_objs> <objsize> <objperslab> <pagesperslab> : tunables <batchcount> <limit> <sharedfactor> : slabdata <active_slabs> <num_slabs> <sharedavail>
> xfs_inode         927591 980848    368   11    1 : tunables   54   27    8 : slabdata  89168  89168      0
> linvfs_icache     927591 980810    384   10    1 : tunables   54   27    8 : slabdata  98081  98081      0
> dentry_cache      645063 703566    144   27    1 : tunables  120   60    8 : slabdata  26058  26058      0
after
 > xfs_inode         828633 980507    368   11    1 : tunables   54   27    8 : slabdata  89137  89137    216
 > linvfs_icache     828629 980220    384   10    1 : tunables   54   27    8 : slabdata  98022  98022    216
 > dentry_cache      571383 703458    144   27    1 : tunables  120   60    8 : slabdata  26054  26054    480

So you're basically drowning in mostly reclaimable slab here. These three entries
are consuming over 800MB of zone_normal alone.

vmstat before
> pginodesteal 36508
> slabs_scanned 56099472
> kswapd_inodesteal 317433
after
> pginodesteal 36536
> slabs_scanned 56443602
> kswapd_inodesteal 317433

The things are being slowly scanned and freed, but it is being pretty lethargic.

Can you try echo 10000 > /proc/sys/vm/vfs_cache_pressure, and see how that goes?

  reply	other threads:[~2004-07-26 11:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-25  9:46 memory not released after using cdrecord/cdrdao (was: audio cd writing causes massive swap and crash) Eduard Bloch
2004-07-26  1:30 ` Ed Sweetman
2004-07-26  9:10   ` OOM-killer going crazy. (was: Re: memory not released after using cdrecord/cdrdao) Jan-Frode Myklebust
2004-07-26 10:55     ` Nick Piggin
2004-07-26 11:10       ` Jan-Frode Myklebust
2004-07-26 11:43         ` Nick Piggin [this message]
2004-07-26 12:46           ` OOM-killer going crazy Jan-Frode Myklebust
2004-07-27  1:00             ` Nick Piggin
2004-07-26 13:02     ` Ed Sweetman
2004-07-27  4:19       ` Nick Piggin
2004-07-27 10:07         ` Jens Axboe
2004-07-27 13:23           ` Ed Sweetman
2004-07-27 13:30             ` Nick Piggin
2004-07-27 22:38               ` Ed Sweetman
2004-07-28  1:00                 ` Nick Piggin
2004-07-28  6:30                   ` Ed Sweetman
2004-07-28  6:45                     ` Jens Axboe
2004-07-28 12:58                       ` Ed Sweetman
2004-07-28 13:31                         ` Jens Axboe
2004-07-29  0:08 ` memory not released after using cdrecord/cdrdao (was: audio cd writing causes massive swap and crash) William Lee Irwin III

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=4104EE5C.406@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=janfrode@parallab.uib.no \
    --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.