Bug #5627
closedmon: scrub mismatch - osdmap mismatch
0%
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?
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.
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.