From: Christopher Kunz <chrislist@de-punkt.de>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: 0.56 scrub OSD memleaks, WAS Re: [0.48.3] OSD memory leak when scrubbing
Date: Mon, 18 Feb 2013 17:46:15 +0100 [thread overview]
Message-ID: <51225AD7.8080606@de-punkt.de> (raw)
In-Reply-To: <511F4CAC.6020405@42on.com>
Am 16.02.13 10:09, schrieb Wido den Hollander:
> On 02/16/2013 08:09 AM, Andrey Korolyov wrote:
>> Can anyone who hit this bug please confirm that your system contains
>> libc 2.15+?
>>
>
Hello,
when we started a deep scrub on our 0.56.2 cluster today, we saw a
massive memleak about 1 hour into the scrub. One OSD claimed over
53GByte within 10 minutes. We had to restart the OSD to keep the cluster
stable.
Another OSD is currently claiming about 27GByte and will be restarted
soon. All circumstantial evidence points to the deep scrub as the source
of the leak.
One affected node is running libc 2.15 (Ubuntu 12.04 LTS), the other one
is using libc 2.11.3 (Debian Squeeze). So it seems this is not a
libc-dependant issue.
We have disabled scrub completely.
Regards,
--ck
PS: Do we have any idea when this will be fixed?
next prev parent reply other threads:[~2013-02-18 16:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 20:01 [0.48.3] OSD memory leak when scrubbing Sylvain Munaut
2013-01-22 21:19 ` Sébastien Han
2013-01-22 21:32 ` Sylvain Munaut
2013-01-22 21:38 ` Sébastien Han
2013-01-25 16:29 ` Sébastien Han
2013-01-25 20:16 ` Sylvain Munaut
2013-01-27 16:17 ` Sylvain Munaut
2013-01-27 17:47 ` Sage Weil
2013-01-27 18:17 ` Sylvain Munaut
2013-01-30 9:12 ` Sylvain Munaut
2013-01-30 9:18 ` Sage Weil
2013-01-30 13:26 ` Sylvain Munaut
2013-01-30 19:40 ` Sage Weil
2013-01-31 13:20 ` Sylvain Munaut
[not found] ` <31226757.422.1359645742478.JavaMail.dspano@it1>
2013-01-31 15:26 ` Sylvain Munaut
2013-01-31 19:57 ` Sage Weil
2013-02-03 18:17 ` Loic Dachary
[not found] ` <CAOLwVUkUFvLihb6KbxG9Et7R_-ZTZpLQJYTjXm9TEe40V_ZRHg@mail.gmail.com>
2013-02-03 21:03 ` Sébastien Han
2013-02-04 17:29 ` Sébastien Han
2013-02-04 19:29 ` Sage Weil
2013-02-04 21:03 ` Dan Mick
2013-02-04 21:08 ` Sébastien Han
2013-02-04 21:22 ` Gregory Farnum
2013-02-04 21:27 ` Sébastien Han
2013-02-16 7:09 ` Andrey Korolyov
2013-02-16 9:09 ` Wido den Hollander
2013-02-17 17:21 ` Sébastien Han
2013-02-18 16:46 ` Christopher Kunz [this message]
2013-02-19 19:23 ` 0.56 scrub OSD memleaks, WAS " Samuel Just
2013-02-19 19:50 ` Christopher Kunz
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=51225AD7.8080606@de-punkt.de \
--to=chrislist@de-punkt.de \
--cc=ceph-devel@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.