From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Just Subject: Re: 0.56 scrub OSD memleaks, WAS Re: [0.48.3] OSD memory leak when scrubbing Date: Tue, 19 Feb 2013 11:23:06 -0800 Message-ID: References: <510EA9A1.6070505@dachary.org> <51102210.2040300@inktank.com> <511F4CAC.6020405@42on.com> <51225AD7.8080606@de-punkt.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from mail-vc0-f170.google.com ([209.85.220.170]:33981 "EHLO mail-vc0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932897Ab3BSTXI (ORCPT ); Tue, 19 Feb 2013 14:23:08 -0500 Received: by mail-vc0-f170.google.com with SMTP id p16so4527017vcq.1 for ; Tue, 19 Feb 2013 11:23:08 -0800 (PST) In-Reply-To: <51225AD7.8080606@de-punkt.de> Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Christopher Kunz Cc: ceph-devel 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 majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html