Project

General

Profile

Actions
Copy link

Bug #6378

closed

mon: osdmap crc mismatch during scrub

Added by Sage Weil over 10 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Joao Eduardo Luis
Category:
Monitor
Target version:
-
% Done:

0%

Source:
Q/A
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

teuthology-2013-09-23_19:00:20-rados-dumpling-testing-basic-plana

had a ~30 scrub mismatch failures. possibly the just-backported full osdmap patches?

Actions
Copy link
 #1

Updated by Joao Eduardo Luis over 10 years ago

basically we're setting different values on 'full_latest' depending on the situation:

  • during trim we set it to the earliest available full map
  • during update_from_paxos, we set it to the latest rebuild full map

so this is triggered in the following scenario:

  • mon A fails
  • leader proposes a trim
  • everybody trims, full_latest = 10
  • mon A comes back and synchronizes
  • mon A updates from paxos, rebuilds latest full_maps because full_latest = 10 and last_committed = 40, and sets full_latest = 40

crc goes boom

Actions
Copy link
 #2

Updated by Sage Weil over 10 years ago

  • Status changed from In Progress to Pending Backport
Actions
Copy link
 #3

Updated by Sage Weil over 10 years ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link

Also available in: Atom PDF