Bug #5627: mon: scrub mismatch - osdmap mismatch - Ceph - Ceph

Actions

Copy link

Bug #5627

closed

mon: scrub mismatch - osdmap mismatch

Added by Denis kaganovich almost 11 years ago. Updated almost 11 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Target version:

% Done:

Source:

other

Tags:

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

Cluster (standard 3 nodes) HEALTH_OK. "ceph scrub" say "scrub mismatch". Mismatched numbers:
mon.0: ... osdmap=1682 ...
mon.1: ... osdmap=1684 ...
mon.2: ... osdmap=1684 ...
Simple restarting mon.0 (leader) not help. Now I purge & re-creating mon.0, all OK, but why database (osdmap) not synced in "healthy" cluster?

Actions

Copy link

Updated by Sage Weil almost 11 years ago

what version exactly are you running?

Actions

Copy link

Updated by Denis kaganovich almost 11 years ago

Monitors - 0.61.4-72-g6af0ed9 (6af0ed9bc4cc955f8c30ad9dc6e9095599f323d0)
osds - not restarted, hmm... looks like 0.61.4-41-gdb2bb27 (db2bb270e93ed44f9252d65d1d4c9b36875d0ea5).
Monitors upgraded and restarted at least twice.

Actions

Copy link

Updated by Sage Weil almost 11 years ago

this is probblay introduced while it was runnign older code (the sha1 you posted is only a day old). as the osdmaps roll over this error will eventually disappear. the bug was only recently fixed, 7fb3804fb860dcd0340dd3f7c39eec4315f8e4b6, late last week.

Actions

Copy link