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: Sat, 16 Aug 2014 20:10:27 +1000 [thread overview]
Message-ID: <20140816201027.4cb2278a@notabene.brown> (raw)
In-Reply-To: <201408160840.s7G8esgf025944@portal.naev.de>
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
On Sat, 16 Aug 2014 10:40:54 +0200 mdraid.pkoch@dfgh.net (Peter Koch) wrote:
> Dear readers,
>
> I am shrinking my raid10-array consiting of 16 2TB disks
> to 13 disks right now. Reshaping runs for 2 hours and
> I'm constantly obervng /proc/mdstat and /proc/meminfo
>
> SUnreclaim is constantly growing while MemFree and
> MemAvailable are decreasing.
>
> Seems like linux 3.14.16 is leaking memory at a rate
> of 4GB per 1TB of reshape data.
Hmm... don't know about that bug.
Does /proc/slabinfo show some slab much bigger than the rest?
>
> My machine has 32GB of RAM and if I interpolate the current
> memory-values I will run out of mem at 80% of the reshape
> operation. This is exactly what happened to me with
> linux-3.14.12.
If you gracefully shutdown and reboot it should keep pick up where it left
off but with more memory free.
>
> Do I need linux-3.14.17 ??
The only bug I know of was fixed in 3.14.6.
I said 3.14.16 before - sorry about typo.
I'll if I can reproduce it myself some time next week.
NeilBrown
>
> Kind regards
>
> Peter Koch
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-08-16 10:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 8:40 memory leak with linux-3.14.16 Peter Koch
2014-08-16 10:10 ` NeilBrown [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-16 13:45 Peter Koch
2014-08-16 20:36 ` NeilBrown
2014-08-17 8:55 Peter Koch
2014-08-18 5:01 ` 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=20140816201027.4cb2278a@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).