Project

General

Profile

Actions
Copy link

Bug #8138

closed

Make PG repair safe by requiring force flag to repair an ambiguous situation

Added by David Zafman about 10 years ago. Updated about 7 years ago.

Status:
Won't Fix
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

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

Description

be_select_auth_object() should have a force flag and not arbitrarily use the first shard as the authoritative object. I have to wonder if in a replicated pool the first shard in the "maps" is always going to be the primary. If a majority have the same checksum that should disambiguate the selection process.

This will allow a UI to provide the repair option without warning messages.

Actions
Copy link
 #1

Updated by David Zafman about 10 years ago

  • Subject changed from Make PG repair safe but requiring force flag to repair an ambiguous situation to Make PG repair safe by requiring force flag to repair an ambiguous situation
Actions
Copy link
 #2

Updated by Sage Weil about 7 years ago

  • Status changed from New to Won't Fix
Actions
Copy link

Also available in: Atom PDF