Project

General

Profile

Actions
Copy link

Bug #3692

closed

OSD's abort with "./common/Mutex.h: 89: FAILED assert(nlock == 0)"

Added by Justin Lott over 11 years ago. Updated over 11 years ago.

Status:
Won't Fix
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Development
Tags:
Backport:
Regression:
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

I've seen this happen twice:

- Reboot a node running a number of OSD's
- Within a short period of time, seemingly random OSD's running on other nodes in the cluster will terminate with the following message:

2012-12-28 16:06:05.919215 7f1f67368700 -1 ./common/Mutex.h: In function 'Mutex::~Mutex()' thread 7f1f67368700 time 2012-12-28 16:06:05.912066
./common/Mutex.h: 89: FAILED assert(nlock == 0)

ceph version 0.48.2argonaut (commit:3e02b2fad88c2a95d9c0c86878f10d1beb780bfe)
 1: /usr/bin/ceph-osd() [0x51546e]
 2: (SimpleMessenger::Pipe::~Pipe()+0x2af) [0x7471ff]
 3: (SimpleMessenger::reaper()+0x50f) [0x782c3f]
 4: (SimpleMessenger::reaper_entry()+0x168) [0x783268]
 5: (SimpleMessenger::ReaperThread::entry()+0xd) [0x74694d]
 6: (()+0x7e9a) [0x7f1f6af48e9a]
 7: (clone()+0x6d) [0x7f1f69be5cbd]
 NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.

Logs are attached. Core dumps are available if desired.

Files

cephlogs.tar.gz (22.4 MB) cephlogs.tar.gz Justin Lott, 12/28/2012 12:01 PM
Actions
Copy link

Also available in: Atom PDF