linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: "Qu Wenruo" <quwenruo@cn.fujitsu.com>,
	"Jérôme Poulin" <jeromepoulin@gmail.com>
Cc: "Andrew E. Mileski" <andrewm@isoar.ca>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs is  related to OOM death problems on my 8GB server with both 3.15.1 and 3.14?
Date: Wed, 16 Jul 2014 08:55:32 -0700	[thread overview]
Message-ID: <20140716155532.GA21186@merlins.org> (raw)
In-Reply-To: <CALJXSJr=PayTcA9z0dsuBu0KRoOKMNRRJfqE4mWAgP8cxopdfg@mail.gmail.com> <53C3313B.1080500@cn.fujitsu.com>

On Mon, Jul 14, 2014 at 09:24:11AM +0800, Qu Wenruo wrote:
> >But generally, is there a tool to locate which kernel function allocated
> >all that RAM that seems to get allocated and forgotten?
> This can be done by kernel memleak detection.
> Location:
> -> Kernel hacking
>     -> Memory Debugging
>         -> Kernel memory leak detector
> 
> Then you can check /sys/kernel/debug/memleak to see which function
> call caused the problem.

I wanted to report back on this.
Unfortunately my laptop with 3.15.5 does not stay up more than 30mn,
sometimes fewer when kmemleak is on. When I turn it off from the boot
command line, the laptop seems to behave ok.

On Tue, Jul 15, 2014 at 08:45:47PM -0400, Jérôme Poulin wrote:
> Hi,
> 
> For this same problem I once got into single user after 2 weeks of
> utilisation and killed all, umounted all FS except root which is ext4,
> rmmod'ed all modules and see by yourself:
> http://i39.tinypic.com/2rrrjtl.jpg
> 
> For those who want it textually:
> 15 days uptime
> 10 user mode processes (systemd, top and bash)
> 2 GB memory usage, 4 GB total memory, 17 MB cache, 32 KB buffers.

Very interesting, thanks for confirming.
So even by removing the btrfs module, the memory was not reclaimed,
correct?

For what it's worth, my server seems ok now that I turned off quotas on
it.

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901

  parent reply	other threads:[~2014-07-16 15:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-04  1:19 Is btrfs related to OOM death problems on my 8GB server with both 3.15.1 and 3.14? Marc MERLIN
2014-07-04  4:33 ` Russell Coker
2014-07-04  6:04   ` Marc MERLIN
2014-07-04  6:23   ` Satoru Takeuchi
2014-07-04 14:24     ` Marc MERLIN
2014-07-04 14:45       ` Russell Coker
2014-07-04 15:07         ` Marc MERLIN
2014-07-04 22:13       ` Duncan
2014-07-05 13:47 ` Andrew E. Mileski
2014-07-05 14:43   ` Marc MERLIN
2014-07-05 15:17     ` Andrew E. Mileski
2014-07-06 14:58     ` Marc MERLIN
2014-07-13 14:29       ` btrfs is " Marc MERLIN
2014-07-13 15:37         ` Marc MERLIN
2014-07-13 15:45           ` btrfs quotas " Marc MERLIN
2014-07-14  1:36             ` Qu Wenruo
2014-07-14  2:43               ` Marc MERLIN
2014-07-14  1:24         ` btrfs is " Qu Wenruo
2014-07-16  0:36           ` Jérôme Poulin
2014-07-16 15:55           ` Marc MERLIN [this message]
2014-07-17  2:22             ` Marc MERLIN
2014-07-16  0:45       ` Is btrfs " Jérôme Poulin
2014-07-05 14:27 ` Andrew E. Mileski

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=20140716155532.GA21186@merlins.org \
    --to=marc@merlins.org \
    --cc=andrewm@isoar.ca \
    --cc=jeromepoulin@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo@cn.fujitsu.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).