Bug: v0.19.0: Reapplying Same Policies Increases Repo Size

[97b4958b055b]

I executed kopia repo create --config-file="$HOME/.config/kopia/repository.config" --path="/media/usb-drive/kopia/repository/" (& all other repo-specific settings the same) after having two existing repos w/ custom .config filenames present, connected. 000 & 001 already had ‘global/not-really-global’ policies applied (or see attached for said policies). I reapplied the same policy set to all three repos to ensure synchronization. Here is the result:

15M     /media/usb-drive/kopia/repository/
28M     /media/usb-drive/kopia/000
28M     /media/usb-drive/kopia/001
20250430T140846UTC

All three repo have yet to have snapshots taken/set up. An 86% increase in storage space usage due to reapplying the same policy set resulting is hardly expected behavior. Restarting the Kopia appimage has no apparent effect.

Bug: v0.19.0: CLI/AppImage: Global Policies Are Not Global

So apparently “global” refers to per repository & not platform wide. Thanks, Obama. Here’s a bash snippet/template to straighten out that nonsense. *nix only. Requirements: fd & ripgrep (rg). Adapt to traditional find & grep if you care to. I don’t. for conf in $(fd config ${HOME}/.config/kopia | rg -v "mlock" | rg -v "password"); do printf "\n%s\n\n" "### Setting global policy for $conf" kopia policy set --config-file="$conf" --global --compression="zstd-better-compression" kopia policy…

---

Related:

Bug: v0.19.0: CLI/GUI/AppImage: repository.config Over-writes Without Warning

So the esteemed minds behind Kopia didn’t bother to write a conditional check against an existing repository.conf and autogen a repository-N.config accordingly. Spectacular. Apparently end users are expected to know beforehand that conf files will be over written unless using --config-file during kopia repo create. I’ve successfully connected three file system repos all under the same volume. Here’s a template: # define conf="$HOME/.config/kopia/fs-000-repo.config" passwd="secret" path="/medi…

[97b4958b055b]

Just for a laugh I applied 'em again:

28M     /media/usb-drive/kopia/repository/
42M     /media/usb-drive/kopia/000
42M     /media/usb-drive/kopia/001
20250430T143018UTC

vs. a trio of freshly created repos with one applied set:

./du.sh && nowutc
15M     /media/usb-drive/kopia/repository
15M     /media/usb-drive/kopia/001
15M     /media/usb-drive/kopia/000
20250501T140540UTC

+180% from baseline. $obligatorilyHitchhikersReferenceHere. The question is… am I laughing with or at you, Kopia devs?