mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: andrew hendry <andrew.hendry@gmail.com>
Cc: kosaki.motohiro@jp.fujitsu.com,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.35-rc1 system oom, many processes killed but memory not free
Date: Fri, 25 Jun 2010 14:00:02 +0900 (JST)	[thread overview]
Message-ID: <20100625133542.8047.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <AANLkTim7CiW-yfugZUAHZCqLvXKgt9CwolCvbLGdCLAk@mail.gmail.com>

> I left a 2.6.35-rc1 system, ubuntu 10.4/64 building randconfigs in a
> ramdisk overnight.
> /dev/ram0              9842848   5141780   4201068  56% /media/ramdisk

your total memory size is 8GB, but ramdisk size is 9.8GB. it's odd settings.

> 
> After about 3 hours oom killer started killing nearly all the
> processes, but the memory is still not released. Could ramdisk cause
> this? How can I find out what is still using all the memory?

Could.
but I'm unclear your case was happen by only ramdisk.
Can you remove such ramdisk at once?

> 
> cat /proc/meminfo
> MemTotal:        8187304 kB
> MemFree:          231976 kB
> Buffers:             424 kB
> Cached:            19728 kB
> SwapCached:        51144 kB
> Active:            14056 kB
> Inactive:          72592 kB
> Active(anon):      12900 kB
> Inactive(anon):    53940 kB
> Active(file):       1156 kB
> Inactive(file):    18652 kB
> Unevictable:           0 kB
> Mlocked:               0 kB
> SwapTotal:       1986556 kB
> SwapFree:        1504676 kB
> Dirty:                 0 kB
> Writeback:         19720 kB
> AnonPages:         32884 kB
> Mapped:             4760 kB
> Shmem:                 4 kB
> Slab:              51652 kB
> SReclaimable:      28816 kB
> SUnreclaim:        22836 kB
> KernelStack:        2880 kB
> PageTables:        18484 kB
> NFS_Unstable:          0 kB
> Bounce:                0 kB
> WritebackTmp:          0 kB
> CommitLimit:     6080208 kB
> Committed_AS:    1133944 kB
> VmallocTotal:   34359738367 kB
> VmallocUsed:      350936 kB
> VmallocChunk:   34359369212 kB
> HardwareCorrupted:     0 kB
> HugePages_Total:       0
> HugePages_Free:        0
> HugePages_Rsvd:        0
> HugePages_Surp:        0
> Hugepagesize:       2048 kB
> DirectMap4k:        7616 kB
> DirectMap2M:     8372224 kB




  reply	other threads:[~2010-06-25  5:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-05  0:46 andrew hendry
2010-06-25  5:00 ` KOSAKI Motohiro [this message]
2010-06-25  5:09   ` Andrew Hendry
2010-06-25  6:16     ` KOSAKI Motohiro

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=20100625133542.8047.A69D9226@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=andrew.hendry@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®