digint / digint/btrbk

Why abort when Received UUID set?

Open
#265 3 comments 0 reactions 0 assignees View on GitHub
question
Dominant language
Perl
Stars
2.1k
Forks
139
PR merge metrics
No merged PRs in 30d

Description

What is the purpose of aborting when the Received UUID is set?

[Line 5365](https://github.com/digint/btrbk/blob/v0.27.1/btrbk#L5364):
```
if($svol->{node}{received_uuid} ne '-') {
ABORTED($svol, "\"Received UUID\" is set");
WARN "Skipping subvolume \"$svol->{PRINT}\": $abrt";
next;
}
```
Is this really necessary?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start in btrbk around line 5365 and trace how received_uuid is populated and used before the abort. Compare the surrounding subvolume handling to determine why this guard exists and whether the current behavior is still required. Done means the rationale and any needed behavior change are established in the issue or an associated change.

Written by the indexing model from the issue text.

Assessment

Tech stack
perl
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.