This bug is showing up a bit for me as well, on Ubuntu. Are we just waiting hopefully for the distros to release new valgrind packages for this to go away, or do we have a plan? I'm concerned that we might not get fixed packages at all — if I'm understanding this correctly it's a result of us running new kernels against "old" valgrind, and the distros obviously don't upgrade their kernels like we are... -Greg On Thu, Feb 4, 2016 at 10:23 PM, <redmine@xxxxxxxxxxxxxxxx> wrote: > Issue #14664 has been reported by Loic Dachary. > ________________________________ > > Bug #14664: valgrind: mmap(...) failed in UME with error 12 (Cannot allocate > memory). > > Author: Loic Dachary > Status: New > Priority: Normal > Assignee: > Category: > Target version: > Source: other > Tags: > Backport: > Regression: No > Severity: 3 - minor > Reviewed: > Affected Versions: > ceph-qa-suite: > Release: > > http://pulpito.ceph.com/loic-2016-02-04_00:33:20-rados-infernalis-backports---basic-multi/6141/ > > CommandFailedError: Command failed on smithi054 with status 1: 'sudo ceph > osd crush tunables default' > > 2016-02-04T01:11:56.731 INFO:teuthology.orchestra.run.smithi054:Running: > 'sudo ceph osd crush tunables default' > 2016-02-04T01:11:56.847 INFO:tasks.ceph.mon.a.smithi054.stderr:valgrind: > mmap(0xaf5000, 131072) failed in UME with error 12 (Cannot allocate memory). > 2016-02-04T01:11:56.848 INFO:tasks.ceph.mon.c.smithi054.stderr:valgrind: > mmap(0xaf5000, 131072) failed in UME with error 12 (Cannot allocate memory). > > ________________________________ > > You have received this notification because you have either subscribed to > it, or are involved in it. > To change your notification preferences, please click here: > http://tracker.ceph.com/my/account -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
