Could we get a feature where we would make bees ignore some subvolumes which I know have high write activity but nearly zero chance of duplicate data blocks?
I imagine such a feature should be possible quite easily in the same way it would ignore read-only snapshots currently, correct? I could imagine putting an empty file at the subvolume root named .beesignore and if bees finds this file, it will add that subvolume to the "blacklist" (?) and handle it like a read-only snapshot.
Could we get a feature where we would make bees ignore some subvolumes which I know have high write activity but nearly zero chance of duplicate data blocks?
I imagine such a feature should be possible quite easily in the same way it would ignore read-only snapshots currently, correct? I could imagine putting an empty file at the subvolume root named
.beesignoreand if bees finds this file, it will add that subvolume to the "blacklist" (?) and handle it like a read-only snapshot.