Have you checked borgbackup docs, FAQ, and open GitHub issues? Yes

Is this a BUG / ISSUE report or a QUESTION? Question

Borg Version borg 1.1.15

Operating system (distribution) and version. Ubuntu 20.04

Hardware / network configuration, and filesystems used. Btrfs

How much data is handled by borg? 750PB (15000 Snapshots of 50GB, 120GB Deduplicated)

Everything is on the same host and disk (a directory is backed up to a borg repository on the same device, no other devices accessing the same repo)

Describe the problem you're observing.

Cancelling (Ctrl-C'ing) a borg info command apparently invalidates the chunks cache, causing an expensive re-build on the next operation (e.g. create)

I don't know what happens under the hood, but borg info feels like it should be a read-only operation, and therefore should not be able to invalidate the cache.

Is this a bug, or expected behaviour?

I cancelled the borg info call because it was taking a long-ish time (~15 minutes)

Many thanks!