Zygo

I handle this by using btrfs snapshots to avoid extra copies: ```bash # one-time setup: btrfs sub create staging # repeatable backup step: rsync -aHS --del src staging && btrfs...

> it may actually be better to use `--no-whole-file --inplace` on btrfs This reminds me to add a disclaimer, especially for anybody who lands here from a search: Please don't...

> Snapshotting isn't an enterprise feature. Indeed. Snapshotting in btrfs is merely a faster way to write `cp -a --reflink=always src dst` on specific src directories, but atomically. If you...

Try the current `master` branch. v0.11 will have significant improvements against this kind of expansion. See #296 for details.

> the range is limited to file system blocks of up to 16MB, which requires looping through these blocks That particular limit was removed from btrfs in Linux kernel v4.18-rc1...

SIGTERM (plain `kill` without -9) and SIGINT (Ctrl-C) are both supported to do orderly termination. Other signals will instantly terminate the bees process. There is a problem with _crashes_, though:...

MRR is a poor fit for production use when firmware may drop writes. If a device loses a write after acknowledging it, all copies may be wrong in the same...

> I can 100% see this be the default for the metadata and system block groups as they're already set to DUP by default for single drives. I see the...

> Inceasing the ability to reconstruct the strong checksum guarantee, i.e. reconstruct correct, checksum-passing, data even if all copies fail the checksum. My question here is not "does MRR help...

sends in general aren't that repeatable. You could run into subtle problems if the extent references in any part of the send changed. This isn't a problem for `btrfs send...