Actions
Bug #8138
closedMake PG repair safe by requiring force flag to repair an ambiguous situation
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