Actions
Bug #7511
closed"set noup; set down <n>; unset noup" doesn't bring <n> back up
Status:
Resolved
Priority:
Immediate
Assignee:
-
Category:
OSD
Target version:
-
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Experiment:
ceph osd set noup
ceph osd down 1
<osd 1 is down>
ceph osd unset noup
Expected:
<osd 1 is back up>
Observed:
<osd 1 stays down>
Sage theorizes that the OSD should notice, when it tries to come back, that noup is set, and subscribe an event from the monitor to notice new maps, so that it sees the
"unset noup" and tries to come back again. (or words to that effect)
Updated by Sage Weil about 10 years ago
- Status changed from New to 12
- Priority changed from Normal to Immediate
ha, this apears to be what is breaking the unit tests on firefly/master:
http://gitbuilder.sepia.ceph.com/gitbuilder-ceph-tarball-precise-amd64-notcmalloc/log.cgi?log=72f260e07cf5f7bc5264a7f8ab292b9dc9ec3222
Updated by Sage Weil about 10 years ago
0> 2014-02-21 21:13:56.428703 7f0258ff9700 -1 osd/PG.cc: In function 'void PG::scrub_finish()' thread 7f0258ff9700 time 2014-02-21 21:13:56.393127
osd/PG.cc: 4294: FAILED assert(deep_scrub)
ceph version 0.77-488-g4a2c0af (4a2c0af22acb51584ccd008b1e991d4943e6b557)
1: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x95) [0x193f819]
2: (PG::scrub_finish()+0x3a2) [0x15f5bc4]
3: (PG::scrub_finalize()+0x2fb) [0x15f56cd]
4: (OSD::ScrubFinalizeWQ::_process(PG*)+0x1d) [0x139d9c7]
5: (ThreadPool::WorkQueue<PG>::_process(PG*, ThreadPool::TPHandle&)+0x32) [0x1429714]
6: (ThreadPool::WorkQueue<PG>::_void_process(void*, ThreadPool::TPHandle&)+0x37) [0x1428cbf]
7: (ThreadPool::worker(ThreadPool::WorkThread*)+0x715) [0x1932283]
8: (ThreadPool::WorkThread::entry()+0x23) [0x1933f21]
Updated by Sage Weil about 10 years ago
- Status changed from 12 to Fix Under Review
Actions