Actions
Bug #16643
closedMDS memory leak in hammer integration testing
Status:
Won't Fix
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Lots of Leak_PossiblyLost and Leak_DefinitelyLost in
smithfarm@teuthology:/a/smithfarm-2016-07-08_15:27:38-fs-hammer-backports---basic-smithi/302718/remote/smithi063/log/valgrind/mds.a-s.log.gz
and
smithfarm@teuthology:/a/smithfarm-2016-07-08_15:27:38-fs-hammer-backports---basic-smithi/302721/remote/smithi046/log/valgrind/mds.a.log.gz
Updated by John Spray almost 8 years ago
- Status changed from New to Won't Fix
MDS leaks are ignored by default in the valgrind task, so presumably you're only seeing this because something else failed?
In any case, these are not believed to be new issues -- when we ultimately get the MDS valgrind clean, we'll do it on master.
Actions