Kai Krakow
Kai Krakow
> This is how I _thought_ it worked, but that is not how it is actually is configured: > > https://github.com/Zygo/bees/blob/081a6af278fc2b4f33198e2ec0028f8383bb6d4a/scripts/beesd%40.service.in#L8 > > https://github.com/Zygo/bees/blob/081a6af278fc2b4f33198e2ec0028f8383bb6d4a/src/bees-usage.txt#L1-L6 > > There doesn't seem to...
If I remember right, SIGBUS is usually only a thing on Linux for processes running off a network mount, and fail to swap in a text segment from their binary,...
You should not use "=" with single letter options... Could you run "bash -x /path/to/beesd your_options"? It looks like the wrapper script cannot parse the supported options from the daemon...
> Does bees report detecting a toxic extent at the same time? Yes, and it already did that since hours before. If you'd need a log of bees from right...
Well, it stalled the whole server. Even ssh into the system did not work although none of the main system is on btrfs but xfs instead, nothing even touches btrfs...
In the last log: nvidia... Do you use multiple monitors?
I wondered if it would be possible to watch the log (or some specialized socket pipeline for that purpose yet to be created) for the files that bees handled, then...
> so it is better to cycle through collecting a few hundred MB of extent data that needs to be relocated I think the max extent size is 128M isn't...
> on rotating media you probably want to batch up more than one temporary extent Ah okay that's the reasoning. Got it.
See also https://github.com/Zygo/bees/issues/31 It was discussed before that bees could sacrifice granularity from 4k to 8k by using btrfs CRC directly from the csum tree, and previous measurements showed that...