Zygo

In order to dedupe an extent, bees must present all references to the extent (e.g. from snapshots, clones, and previous dedupes by other tools) to the dedupe ioctl where they...

refs=0 occurs when the hash table contains an entry for an extent that has been deleted after it was added to the hash table. The extent lookup returns 0 refs....

Large files are also a bad case for LOGICAL_INO. A lot of things seem to be bad cases for LOGICAL_INO. If you look up the blocks near the above, e.g....

Some statistics I compiled on PERFORMANCE warnings: ``` $ for x in stats/beestest-*/log.txt; do echo "--- $x ---"; sed -nr 's/.*PERFORMANCE.*sec:.([^ ]+).*/\1/p' < "$x" | sort | uniq -dc |...

`btrfs ins log` operates on the extent tree, so there is no subvol in the input. The output of LOGICAL_INO is a list of (subvol, ino, offset) tuples. Maybe we...

Resolving has long been one of the bottlenecks in bees. It used to be four orders of magnitude slower. Now at least in some storage layer configurations it's not the...

I started at 10s, then cut it in half twice. It is a pretty arbitrary number that is highly dependent on the performance characteristics of the filesystem's lower storage layers;...

That would require... * getting the btrfs device tree * mapping that to Linux devices * mapping those, lsblk-style, back to /sys/block/* which seems like a lot of extra code...

Yeah this one is breaking out of a finite loop with billions of possible iterations. Like #99, we have to cross a dozen stack frames to kill a loop, so...

This will get triggered a lot when the data consists of adjacent repeating blocks. These are not good candidates for dedupe with the existing algorithms, and they're also hard to...