Kopia cache limit bug

General Topics
1

kopia cache shows this information

kopia\2afbd561528f7fbd\contents: 70954 files 36.5 GB (limit 5.2 GB ...)

What does limit 5.2GB actually mean?

2

I think that is the default size of the local kopia cache, so it will try its best to be below 5G unless told to use another size. The local cache contains lists of files+dates and checksums that exist on the remote side so that your local instance of kopia knows when it can skip sending a chunk of data, since it exists on the remote side already. If the local cache is too small, it will have to re-fetch these lists from the remote more often.

3

it will try its best to be below 5G

What’s the range for 'try its best"? My cache size is 36.5GB (see also the output mentioned in the OP), but the limit is only 5.2GB. It seems like a bug, right?

4

Here is good thread about Kopia and its cache usage:

5

Thanks. Could you please comment, whether it is a bug or normal that Kopia exceeds the cache limit of 5GB by 30GB?

6

Are you running a Kopia client/server setup or are you running KopiaUI?

7

kopia cli

(Post must be at least 20 characters0

8

Ok, well… that doesn’t tell us much. I was referring to your setup in general. Do you run only KopiaUI (which includes a local instance of Kopia server under the hood), or do you run a Kopia server on one host and a Kopia client on another.

9

I don’t use neither. With “kopia cli” I meant to say “I run Kopia from the command line interface”. No server, no UI - AFAIK.

10

Alright… I went to check on my repos and sure enough, the size of my cache folder is way higher than has been configred in the repo config. Its no big issue for me, as I do have a couple of TBs on SSD available, which is where I put the cache folder onto, but 524G vs. 32G (configured) is a lot.

However, it looks like, I need to rework my repo config file, which is rather old. As the latest Kopia docs suggest, options have been renamed or reworked.

11

Thanks. So that looks like a bug indeed …