Project

General

Profile

Actions

Bug #23267

closed

scrub errors not cleared on replicas can cause inconsistent pg state when replica takes over primary

Added by David Zafman about 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
David Zafman
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
luminous, jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

The PG_STATE_INCONSISTENT flag is set based on num_scrub_errors. A pg query can show after scrub inconsistencies repaired the non-primaries still showing num_scrub_errors > 0 in there local object_stat_sum_t. If a non-primary like that becomes primary the inconsistent pg state can re-appear until another scrub/deep-scrub clears num_scrub_errors.


Related issues 3 (0 open3 closed)

Related to RADOS - Bug #23576: osd: active+clean+inconsistent pg will not scrub or repairCan't reproduceDavid Zafman04/06/2018

Actions
Copied to RADOS - Backport #23485: luminous: scrub errors not cleared on replicas can cause inconsistent pg state when replica takes over primaryResolvedDavid ZafmanActions
Copied to RADOS - Backport #23486: jewel: scrub errors not cleared on replicas can cause inconsistent pg state when replica takes over primaryResolvedDavid ZafmanActions
Actions

Also available in: Atom PDF