Project

General

Profile

Actions

Bug #3566

closed

log max new = 1 can cause hang on process exit

Added by Dan Mick over 11 years ago. Updated about 11 years ago.

Status:
Resolved
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

Investigating other things entirely, I had set log max err = 1 in [global]; I started
observing occasional hangs, and could not explain; instrumenting a loop of
while true; rbd rm <nonexistent>; done
I noticed the hang after rbd finished the
last statement of the Rados destructor, which is the last thing I could think to instrument.
gdb got garbage and uninterpretable stacks. I found the log setting by accident.

I suspect some kind of memory corruption with the Log destructor racing against log
calls, but that's only based on a half-analysis of the problem, not any actual evidence.

Actions #1

Updated by Dan Mick over 11 years ago

  • Description updated (diff)
Actions #2

Updated by Dan Mick over 11 years ago

  • Description updated (diff)
Actions #3

Updated by Dan Mick over 11 years ago

  • Assignee set to Sage Weil
Actions #4

Updated by Sage Weil about 11 years ago

  • Status changed from New to Resolved

fixed a few weeks ago, commit:813787af3dbb99e42f481af670c4bb0e254e4432 and a few prior commits

Actions

Also available in: Atom PDF