Closed Sporif closed 2 years ago
Thank you for filing this issue.
Maybe.
I'm reluctant to add support for every way btrfs can be snapshot-ed. I'd like to find a more sustainable way to support more use cases in btrfs without having to spend any time testing them myself as I am a ZFS guy.
I'm also very reluctant to read from any config file. Parsing mounts is bad enough.
I am more likely to support something that can cover many use cases. If you/anyone can think of a better way, I'm all ears. I'm open to ideas.
To editorialize a little bit, this is why I didn't want to support btrfs. Because if I can't make every filesystem layout work, someone is going to be disappointed. IMHO btrfs should have done what ZFS did and defined a .btrfs
directory for snapshots. Maybe it would be better that btrfs users ask for this from the btrfs developers, then I try to support every uses.
You might try: https://github.com/kimono-koans/httm/pull/36
Should be slower than it would be otherwise, but should fit all btrfs use cases.
Thanks!
I saw you added Btrfs support via snapper and timeshift. Is it possible to also add support for btrbk? It produces snapshots according to its configuration file. It has a subcommand
btrbk list source
that when run shows the source subvolume, snapshot subvolume and the snapshot name.For example with this config file:
the command
btrbk list source
produces this output:And if I list the snapshots with
sudo btrbk list snapshots
: