From: Mark Nelson <mark.nelson@inktank.com>
To: Ranjan Sarpangala Venkatesh <ranjansv@soe.ucsc.edu>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Using valgrind_osd option
Date: Tue, 09 Jul 2013 20:15:02 -0500 [thread overview]
Message-ID: <51DCB596.4040800@inktank.com> (raw)
In-Reply-To: <CA+bvTtnt_GZEiwHgsmW_uWvjhFxE3QxyUTWX=nM6hs5E6ikLuQ@mail.gmail.com>
Hi,
I ran into this problem a while back and it was because I was trying to
use a version of valgrind that didn't support tcmalloc (which Ceph was
compiled to use). Try upgrading valgrind to 3.8.0 or newer. You'll
also need to pass something like:
--soname-synonyms=somalloc=*tcmalloc*
Mark
On 07/09/2013 08:10 PM, Ranjan Sarpangala Venkatesh wrote:
> Hi,
>
> I am trying to collect memory of the OSD daemon with the following
>
> ./vstart.sh -n -x -l --valgrind_osd 'massif'
>
> However, when I print massif.out file there is nothing
>
> cat massif.out.15391
>
> desc: (none)
> cmd: ./ceph-osd -i 0 -c ceph.conf -f
> time_unit: i
> #-----------
> snapshot=0
> #-----------
> time=0
> mem_heap_B=0
> mem_heap_extra_B=0
> mem_stacks_B=0
> heap_tree=empty
>
> --
> With regards,
> Ranjan
> --
> 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
>
next prev parent reply other threads:[~2013-07-10 1:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 1:10 Using valgrind_osd option Ranjan Sarpangala Venkatesh
2013-07-10 1:15 ` Mark Nelson [this message]
2013-07-11 6:21 ` Ranjan Sarpangala Venkatesh
2013-07-11 19:38 ` Sage Weil
2013-07-11 20:21 ` Mark Nelson
2013-07-12 6:45 ` Ranjan Sarpangala Venkatesh
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=51DCB596.4040800@inktank.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ranjansv@soe.ucsc.edu \
/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.