Project

General

Profile

Actions
Copy link

Bug #20416

closed

"FAILED assert(osdmap->test_flag((1<<15)))" (sortbitwise) on upgraded cluster

Added by Hey Pas almost 7 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Greg Farnum
Category:
-
Target version:
-
% Done:

0%

Source:
Community (user)
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
Ceph - v12.1.0
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Hello,

I've upgraded a Jewel cluster to Luminous 12.1.0 (RC), restarted the monitors, mgr is active, but I can't restart the first OSD, as it gives a very nasty strack trace with an assertion error claiming that

2017-06-26 11:49:56.786744 7f83963d7700 1 /build/ceph-12.1.0/src/osd/PG.cc: In function 'void PG::on_new_interval()' thread 7f83963d7700 time 2017-06-26 11:49:56.780364
/build/ceph-12.1.0/src/osd/PG.cc: 5412: FAILED assert(osdmap>test_flag((1<<15)))

I guess this is the check for sortbitwise ( https://github.com/ceph/ceph/blob/288f623878284c7025f0197d24b2689a6cbb3af6/src/osd/PG.cc#L5412 )

The problem is, I can't set sortbitwise.

After executing ceph osd set sortbitwise (the mon logs confirm that the command finished), ceph status doesn't show the osdmap/flags section.

Is there any way to set the flag via lower level commands/manually? Or it's easier just to trash the OSD and somehow create a new one? (This is a 3 osd mini cluster, but size is 3 [with min_size = 2] for important pools.)

This is on Ubuntu Trusty.

Actions
Copy link

Also available in: Atom PDF