Can you confirm that the memory size reported is res?
-Sam
On Mon, Feb 18, 2013 at 8:46 AM, Christopher Kunz wrote:
> 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?
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html