mirror of
https://github.com/Zygo/bees.git
synced 2025-05-17 13:25:45 +02:00
d384f3eec0
Previously, when the bees send workaround is enabled, bees would immediately advance the subvol's crawl status as if the entire subvol had been scanned. If the subvol is later made read-write, or if the workaround is disabled, bees sees that the subvol has already been marked as scanned. This is an unfortunate result if the subvol is inadvertently marked read-only or if bees is inadvertently run with the send workaround disabled. Instead, (almost) completely ignore the subvol: don't advance the crawl pointer, don't consider the subvol in the list if searchable roots, and don't consider the subvol when calculating min_transid for new subvols. The "almost" part is: if the subvol scan has not yet started, keep its start timestamp current so it won't mess up subvol traversal performance metrics. Also handle exceptions while determining whether a subvol is read-only, as those apparently do happen. Signed-off-by: Zygo Blaxell <bees@furryterror.org>
BEES
Best-Effort Extent-Same, a btrfs deduplication agent.
About bees
bees is a block-oriented userspace deduplication agent designed for large btrfs filesystems. It is an offline dedupe combined with an incremental data scan capability to minimize time data spends on disk from write to dedupe.
Strengths
- Space-efficient hash table and matching algorithms - can use as little as 1 GB hash table per 10 TB unique data (0.1GB/TB)
- Daemon incrementally dedupes new data using btrfs tree search
- Works with btrfs compression - dedupe any combination of compressed and uncompressed files
- NEW Works around
btrfs sendproblems with dedupe and incremental parent shapshots - Works around btrfs filesystem structure to free more disk space
- Persistent hash table for rapid restart after shutdown
- Whole-filesystem dedupe - including snapshots
- Constant hash table size - no increased RAM usage if data set becomes larger
- Works on live data - no scheduled downtime required
- Automatic self-throttling based on system load
Weaknesses
- Whole-filesystem dedupe - has no include/exclude filters, does not accept file lists
- Requires root privilege (or
CAP_SYS_ADMIN) - First run may require temporary disk space for extent reorganization
- First run may increase metadata space usage if many snapshots exist
- Constant hash table size - no decreased RAM usage if data set becomes smaller
- btrfs only
Installation and Usage
Recommended Reading
- bees Gotchas
- btrfs kernel bugs - especially DATA CORRUPTION WARNING
- bees vs. other btrfs features
- What to do when something goes wrong
More Information
Bug Reports and Contributions
Email bug reports and patches to Zygo Blaxell bees@furryterror.org.
You can also use Github:
https://github.com/Zygo/bees
Copyright & License
Copyright 2015-2018 Zygo Blaxell bees@furryterror.org.
GPL (version 3 or later).