Zygo

I think you're just going to have to fix gcc for this one. I can't reproduce this on Debian's g++-13 (Debian 13.1.0-1). I could reproduce two other build failures on...

I got a build failure from `-D_GLIBCXX_ASSERTIONS` (in `ntoa.cc` of all places) on the random version of gcc 12 I had lying around, which promptly disappeared after upgrading the compiler...

> Afaik the following recent doc updates indicate this -c 1 workaround to avoid the freezes isn't needed any more - can you confirm that? Yes. Commit a2e1887c525c3c2ef3e8daeb787ccb21f255eff7 prevents bees...

Commit 3839690 probably fixes this issue too. Please test.

For reasons I cannot fathom, `reinterpret_cast(32-bit-pointer)` interprets `pointer` as a _signed_ integer. That puts 32 one bits in the top half of the address, which results in `EFAULT` when 32-bit...

You can change the writeback rate in `src/bees.h`: ``` // Bytes per second we want to flush (8GB every two hours) const double BEES_FLUSH_RATE = 8.0 * 1024 * 1024...

The hash table is excluded already. `beescrawl.dat` and `beesstats.txt` are not, but they will generate only a few pages of IO activity every writeback interval (15 minutes). They could be...

`beescrawl.dat` stores the point where bees has reached in the filesystem scan. Removing `beescrawl.dat` causes bees to restart from the beginning of the filesystem and reinsert hashes of all data...

See `find_live_mirror` in [`fs/btrfs/volumes.c`](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/fs/btrfs/volumes.c#n6070). There is a read policy framework which would allow defining better read policies, but to date only one has been implemented: the PID policy, which assigns...

> it would be nice if this section reflected the current possible profiles (add in raid1c3/raid1c4) for the order of selection. Currently, the kernel doesn't define the order of selection...