Axel Burri

This is a nice idea, but it's incomplete: As btrbk is stateless, it always needs information of which subvolumes are already present on the target side. For `target send-receive`, this...

Yeah well, but then people start deleting files on the target by hand, and the mess with the journal starts... I guess glacier also provides some sort of directory listing,...

> However, my idea was that the pipe target would be a fire-and-forget kind of a thing Yes I understand, and I see the benefit in this, but that's not...

Sounds useful. Something like `snapshot_name_prefix_fullpath [yes|no]`, or even `snapshot_name_prefix_path_from /my/root/path/`. Adding "enhancement" label on this (don't expect it too soon, I'm pretty busy at the moment...)

This behavior has changed, along with many improvements/cleanup regarding the "list" actions in v0.31.1. The main reason for that was that "btrbk list snapshots" in v0.30.0 listed snapshots multiple times...

I think the main confusion here is the term "regardless of how many there are". Make sure to understand how the retention mechanism works: e.g. btrbk does not differtiate if...

Added some documentation in 4d1b9119475f5d91c2b96c6b1b1a5ef8f9eec323, thanks for your suggestions!

While I'm sure that from a technical point the documentation is correct and comprehensive, I agree that it's not that easy to understand. I've tried to make it clear on...

Try setting the `compat` in your config. Or more specifically, set `compat_remote` in the target section pointing to your NAS.

> Apparently, in recent versions of btrfs-progs, it is possible to use the -u option of btrfstune to assign an arbitrary UUID. I am currently trying this (this takes a...