Ceph » CephFS

@Venky Shankar How do I interpret this ?
I don't see any frame pointing to a ceph file apart from the initial finger pointing to ceph-mds.

<?xml version="1.0"?>

<valgrindoutput>

<protocolversion>4</protocolversion>
<protocoltool>memcheck</protocoltool>

<preamble>
  <line>Memcheck, a memory error detector</line>
  <line>Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.</line>
  <line>Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info</line>
  <line>Command: ceph-mds -f --cluster ceph -i b</line>
</preamble>

<pid>68459</pid>
<ppid>68448</ppid>
<tool>memcheck</tool>

<args>
  <vargv>
    <exe>/usr/bin/valgrind</exe>
    <arg>--trace-children=no</arg>
    <arg>--child-silent-after-fork=yes</arg>
    <arg>--soname-synonyms=somalloc=*tcmalloc*</arg>
    <arg>--num-callers=50</arg>
    <arg>--suppressions=/home/ubuntu/cephtest/valgrind.supp</arg>
    <arg>--xml=yes</arg>
    <arg>--xml-file=/var/log/ceph/valgrind/mds.b.log</arg>
    <arg>--time-stamp=yes</arg>
    <arg>--vgdb=yes</arg>
    <arg>--exit-on-first-error=yes</arg>
    <arg>--error-exitcode=42</arg>
    <arg>--tool=memcheck</arg>
  </vargv>
  <argv>
    <exe>ceph-mds</exe>
    <arg>-f</arg>
    <arg>--cluster</arg>
    <arg>ceph</arg>
    <arg>-i</arg>
    <arg>b</arg>
  </argv>
</args>

<status>
  <state>RUNNING</state>
  <time>00:00:00:00.060 </time>
</status>

<status>
  <state>FINISHED</state>
  <time>00:00:33:36.844 </time>
</status>

<error>
  <unique>0x3137</unique>
  <tid>1</tid>
  <threadname>ceph-mds</threadname>
  <kind>Leak_PossiblyLost</kind>
  <xwhat>
    <text>32 bytes in 1 blocks are possibly lost in loss record 1,308 of 3,147</text>
    <leakedbytes>32</leakedbytes>
    <leakedblocks>1</leakedblocks>
  </xwhat>
  <stack>
    <frame>
      <ip>0x484BF70</ip>
      <obj>/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so</obj>
      <fn>calloc</fn>
      <dir>/builddir/build/BUILD/valgrind-3.22.0/coregrind/m_replacemalloc</dir>
      <file>vg_replace_malloc.c</file>
      <line>1595</line>
    </frame>
    <frame>
      <ip>0x62BD6A5</ip>
      <obj>/usr/lib64/libnl-3.so.200.26.0</obj>
      <fn>__trans_list_add</fn>
    </frame>
    <frame>
      <ip>0x6232F1E</ip>
      <obj>/usr/lib64/libnl-route-3.so.200.26.0</obj>
    </frame>
    <frame>
      <ip>0x400507D</ip>
      <obj>/usr/lib64/ld-linux-x86-64.so.2</obj>
      <fn>call_init</fn>
      <dir>/usr/src/debug/glibc-2.34-105.el9.x86_64/elf</dir>
      <file>dl-init.c</file>
      <line>70</line>
    </frame>
    <frame>
      <ip>0x400507D</ip>
      <obj>/usr/lib64/ld-linux-x86-64.so.2</obj>
      <fn>call_init</fn>
      <dir>/usr/src/debug/glibc-2.34-105.el9.x86_64/elf</dir>
      <file>dl-init.c</file>
      <line>26</line>
    </frame>
    <frame>
      <ip>0x400516B</ip>
      <obj>/usr/lib64/ld-linux-x86-64.so.2</obj>
      <fn>_dl_init</fn>
      <dir>/usr/src/debug/glibc-2.34-105.el9.x86_64/elf</dir>
      <file>dl-init.c</file>
      <line>117</line>
    </frame>
    <frame>
      <ip>0x401CC29</ip>
      <obj>/usr/lib64/ld-linux-x86-64.so.2</obj>
    </frame>
    <frame>
      <ip>0x5</ip>
    </frame>
    <frame>
      <ip>0x1FFF000C1E</ip>
    </frame>
    <frame>
      <ip>0x1FFF000C27</ip>
    </frame>
    <frame>
      <ip>0x1FFF000C2A</ip>
    </frame>
    <frame>
      <ip>0x1FFF000C34</ip>
    </frame>
    <frame>
      <ip>0x1FFF000C39</ip>
    </frame>
    <frame>
      <ip>0x1FFF000C3C</ip>
    </frame>
  </stack>
</error>

</valgrindoutput>

Milind Changire wrote in #note-2:

@Venky Shankar How do I interpret this ?
I don't see any frame pointing to a ceph file apart from the initial finger pointing to ceph-mds.

That's correct. The traceback doesn't seem to point to anything on the ceph-mds side apart from some malloc frame (I think that's related to tcmalloc).

We should try to suppress this warning. Otherwise, I guess the online-data PR is mostly good to merge. yay!