Unused blobs not being pruned

Support
1

The size of my repository is now 1.5 TB. Running kopia maintenance run --full --safety=none shows GC found 1162783 unused contents (1.2 TB) but it only further increases the repository size. The repository owner is set to the machine I ran the maintenance command on and automatic maintenance is on.

`> kopia maintenance run --full --safety=none
Found too many index blobs (13155), this may result in degraded performance.

Please ensure periodic repository maintenance is enabled or run ‘kopia maintenance’.
Running full maintenance…
Found too many index blobs (13155), this may result in degraded performance.

Please ensure periodic repository maintenance is enabled or run ‘kopia maintenance’.
GC found 1162783 unused contents (1.2 TB)
GC found 0 unused contents that are too recent to delete (0 B)
GC found 482065 in-use contents (276.4 GB)
GC found 13619 in-use system-contents (295.1 MB)
GC undeleted 0 contents (0 B)
Found too many index blobs (13191), this may result in degraded performance.

Please ensure periodic repository maintenance is enabled or run ‘kopia maintenance’.
Compacting an eligible uncompacted epoch…
Advancing epoch markers…
Attempting to compact a range of epoch indexes …
Cleaning up unneeded epoch markers…
Cleaning up old index blobs which have already been compacted…
Cleaned up 16 logs.
Finished full maintenance.`

kopia maintenance output:


Found too many index blobs (13354), this may result in degraded performance.

Please ensure periodic repository maintenance is enabled or run ‘kopia maintenance’.
Owner: root@g11
Quick Cycle:
scheduled: true
interval: 1h0m0s
next run: 2026-03-15 09:51:51 CET (in 26m58s)
Full Cycle:
scheduled: true
interval: 24h0m0s
next run: 2026-03-15 19:28:54 CET (in 10h4m1s)
Log Retention:
max count:       10000
max age of logs: 720h0m0s
max total size:  1.1 GB

Does anyone know how to fix this?

2

I have same issue and I solve it by exec
kopia maintenance run --full --safety=none --force

3

I tried that but it just grew further :frowning:. I created a new repository, but that one has already grown to 1 TB too. kopia maintenance run also only detects 153.8 GB of used objects despite the 1 TB total size.

root@Kopia:/app# kopia maintenance run --full --safety=none --force
Running full maintenance...
GC found 50462 unused contents (41.1 GB)
GC found 0 unused contents that are too recent to delete (0 B)
GC found 617443 in-use contents (153.8 GB)
GC found 1664 in-use system-contents (23.1 MB)
GC undeleted 0 contents (0 B)
Compacting an eligible uncompacted epoch...
Advancing epoch markers...
Attempting to compact a range of epoch indexes ...
Cleaning up unneeded epoch markers...
Cleaning up old index blobs which have already been compacted...
Cleaned up 1 logs.
Finished full maintenance.

4

Possible that it has nothing to do with kopia itself. What is your repo destination?

5

I’m storing it using Backblaze B2

:sweat_smile: oops, that explains the issues with the second repository.

Screenshot showing "Keep all file versions" is enabled
Screenshot showing "Keep all file versions" is enabled527×206 11.8 KB

That said the previous repository I was having issues with (from the first post in this thread) does use the right setting (“Keep only the last version of the file”), so I still don’t really know why it was having issues.

6

You are not the first one making this mistake.

There is no known issue with kopia pruning AFAIK. so double check B2 settings. Especially that what you described looks like your storage keeping everything (including deleted files) - some sort of versioning outside kopia scope.