Filtering on can_mount == 'on' prevents backing up root ZFS datasets #1269
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 project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
borgmatic-collective/borgmatic#1269
Loading…
Add table
Add a link
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 back up a root ZFS dataset after following the official guide.
I marked
rpoolwithorg.torsion.borgmatic:backup=auto, which makes the rest of the datasets inherit the marker. However, with--verbose 2I can see that while borgmatic mounts datasets, it skipsrpool/ROOT/debianmounted onroot.After looking through the code, I think I know the reason:
if can_mount == 'on'The datasets are filtered with
can_mount == 'on', rather than withcan_mount != 'off'. My root dataset (rpool/ROOT/debian) hascanmount == 'noauto', so while it can be mounted, it is still skipped as if it's unmountable.borgmatic version
1.9.14
borgmatic installation method
Debian package
Borg version
1.4.0
Python version
3.13.5
Operating system and version
Debian GNU/Linux 13 (trixie)
Thanks for filing this with all of the details! It's fixed in main now and will be part of the next release.
That's was insanely quick haha. Thank you!
Caught me at a good time!
Released in borgmatic 2.1.3!