Project

General

Profile

Actions
Copy link

Bug #16880

closed

saw valgrind issue <kind>Leak_StillReachable</kind> in /var/log/ceph/valgrind/client.0.log

Added by Jeff Layton over 7 years ago. Updated over 7 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
fs
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

One of my "fs" test runs over the weekend failed with this:

2016-07-30T21:21:57.087 ERROR:tasks.ceph:saw valgrind issue   <kind>Leak_StillReachable</kind> in /var/log/ceph/valgrind/client.0.log
http://pulpito.ceph.com/jlayton-2016-07-29_18:51:42-fs-wip-jlayton-nlink---basic-mira/341560/

Still trying to track down the log to see what leaked.

Actions
Copy link
 #1

Updated by Jeff Layton over 7 years ago

client.0.log is here:

http://qa-proxy.ceph.com/teuthology/jlayton-2016-07-29_18:51:42-fs-wip-jlayton-nlink---basic-mira/341560/remote/mira119/log/valgrind/client.0.log.gz
  <kind>Leak_StillReachable</kind>
  <xwhat>
    <text>8 bytes in 1 blocks are still reachable in loss record 13 of 66</text>

I'm not very adept at deciphering valgrind XML output however, so I won't try to post the stack trace, but looks like it's down in the bowels of the boost libs?

Actions
Copy link
 #2

Updated by John Spray over 7 years ago

  • Status changed from New to Duplicate

See:
http://tracker.ceph.com/issues/14794
http://tracker.ceph.com/issues/15356

(aka The Mystery Of the Valgrind Exception That Doesn't Work on CentOS)

Actions
Copy link

Also available in: Atom PDF