Is your feature request related to a problem? Please describe.
Currently, the repair command automatically selects the CTDB entry with the highest confidence when multiple repairable entries are available. While this is a good default behavior, there are cases where a user might want to explicitly select a different parity data entry for repair.
Proposed Solution
Add a --target <id> option to the repair command.
- If
--target <id> is specified, use the entry corresponding to that ID (e.g., 1-based index from the verify output).
- If
--target is not specified, fall back to the current default behavior of selecting the entry with the highest confidence.
This will give users more control over the repair process when multiple valid entries exist in the database.
Is your feature request related to a problem? Please describe.
Currently, the
repaircommand automatically selects the CTDB entry with the highest confidence when multiple repairable entries are available. While this is a good default behavior, there are cases where a user might want to explicitly select a different parity data entry for repair.Proposed Solution
Add a
--target <id>option to therepaircommand.--target <id>is specified, use the entry corresponding to that ID (e.g., 1-based index from the verify output).--targetis not specified, fall back to the current default behavior of selecting the entry with the highest confidence.This will give users more control over the repair process when multiple valid entries exist in the database.