Kai Krakow
Kai Krakow
I'm using restic or borg to store my backup on Synology instead of sending snapshots. It compresses and deduplicates better, and is not affected by copied files which would not...
> Next, you say you snapshot the borg repo on the NAS with retention. I guess the snapshotting of the compressed binary borg repo is not optimal with CoW, same...
I think Synology uses their custom btrfs patches and pretty old kernels - so I suppose better not run bees on it: It would cause running very very untested codepaths....
So in the context of the original question: Yeah, Synology NAS is designed around the software features implemented. Btrfs should be supported by most current models. But only the stronger...
This is probably the same as #257. I can observe this behavior since switching from LTS 5.19 to 6.1. It's not that bees occupies free memory, it's rather btrfs seems...
> If this does work, then maybe a workaround is possible: use the small buffer size at first, but if the buffer fills up, then switch to the larger buffer....
So bees could dynamically increase that number by 64k up to 3 times until we pass around 10k references. So if it would get exactly 2730 refs, it would use...
> We don't want to do more than two requests for any given block, since all of the prior work is wasted when we repeat the request, and the large...
Okay but in theory, bigger extents tend to have fewer refs - statistically. So in the end, such a "resubmit" because of a small buffer would not happen anyways, and...
> with a year's worth of snapshots You mean: daily snapshots? hourly?