Cannot dry-run with LVM #1093
Labels
No labels
blocked
breaking
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No milestone
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
borgmatic-collective/borgmatic#1093
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'm trying to do and why
I'm trying to run a dry-run of borgmatic by running
borgmatic -n. It cannot go through all the steps, and instead tries again. Until it fails.Steps to reproduce
borgmatic -nActual behavior
Expected behavior
borgmatic handles whatever the issue is (lacking LVM snapshots) in dry-run mode and proceeds with the dry-run
Other notes / implementation ideas
No response
borgmatic version
1.9.14
borgmatic installation method
Alpine Linux
Borg version
borg 1.4.0
Python version
Python 3.12.10
Database version (if applicable)
No response
Operating system and version
Alpine Linux v3.21
Thanks for filing this. Looking at the code, it appears that borgmatic is being a little too optimistic in what LVM hook code it's running during a dry run. Fortunately, the fix looks pretty straightforward: during a dry run, skip slightly more code than is being skipped now.
This is fixed in main and will be part of the next release!
Released in borgmatic 2.0.6!