From: NeilBrown <neilb@suse.de>
To: Peter Koch <mdraid.pkoch@dfgh.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: memory leak with linux-3.14.16
Date: Sun, 17 Aug 2014 06:36:58 +1000 [thread overview]
Message-ID: <20140817063658.79406706@notabene.brown> (raw)
In-Reply-To: <201408161345.s7GDj5gR027016@portal.naev.de>
[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]
On Sat, 16 Aug 2014 15:45:05 +0200 mdraid.pkoch@dfgh.net (Peter Koch) wrote:
> Dear Neil,
>
> > The only bug I know of was fixed in 3.14.6.
> > I said 3.14.16 before - sorry about typo.
>
> No wonder 3.14.16 behaves exactly as 3.14.12 did
>
> My server now has reshaped 2.28TB and lost 9.14GB of RAM
> so memory is still leaking at 4GB per TB
>
> > Hmm... don't know about that bug.
> > Does /proc/slabinfo show some slab much bigger than the rest?
>
> I'm not a memory expert, so I made a copy of /proc/slabinfo and
> compared this copy with /proc/slabinfo in an endless loop.
>
> There are two values which are unusually high and
> are going up constantly:
>
> radix_tree_node 403942
> kmalloc-256 38283576
>
> 38283576 chunks of 256 bytes are exactly those 9.14GB of
> RAM that have leaked so far.
>
> > If you gracefully shutdown and reboot it should keep pick up where it left
> > off but with more memory free.
>
> Last time my machine crashed when about 10TB of data was reshaped.
> And my machine has 32GB of RAM plus 8GB of swap. According to my
> calculations I need 13TB * 4GB/TB = 52GB of RAM, so adding another
> 20GB of swapspace should keep my server running until the reshape
> has finished.
That won't help. Data stored in kmalloc-256 won't get swapped out - it stays
in RAM. So unless you can hot-plus 20Gig of RAM ....
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-08-16 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 13:45 memory leak with linux-3.14.16 Peter Koch
2014-08-16 20:36 ` NeilBrown [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-17 8:55 Peter Koch
2014-08-18 5:01 ` NeilBrown
2014-08-16 8:40 Peter Koch
2014-08-16 10:10 ` NeilBrown
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=20140817063658.79406706@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=mdraid.pkoch@dfgh.net \
/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).