Kai Krakow

I think using the timeout command is perfectly fine... You should probably use a timeout that's a few seconds (or 2-3 minutes) more than a 15 minute block to not...

I think those who are interested in one of the particular ideas should create a separate issue limited to one idea each.

Actually, I don't see why that is because `-Werror` shouldn't depend on the optimization level. It's probably one of the optimization flags that will be enabled at `-O1` (it working...

Bees needs to run from subvolume 5, and it also stores its database there. So it works as designed. But if you didn't use the wrapper that actually mounts subvol...

I reported these previously. Most important: Your data is safe, nothing to worry about. What bees is seeing here is a huge huge pile of small identical blocks. Reflinking all...

I suggest lowering the log level, most of this is uninteresting stuff and not useful for unattended operation of the daemon. I'm using `--verbose=5` on all systems. The bars come...

Oh yeah, I once again forgot that multiple blocks in sequence can and are matched only by the hash of the first block in the sequence. Now `d` and `D`...

I've seen similar dmesg logs lately (hung task with btrfs calls in the backtrace) but not triggered by bees for me. I'm seeing it when Steam downloads data at 100...

"toxic extents" are extents that require more time to process in the kernel than a specified (hard-coded) timeout. Bees will remove those from the hash table as far as I...

I was under the impression that "abandoned toxic match" means discarding the hash from the table, and future duplicates would be created from another copy of the extent. But since...