Michael Eischer

36 TB is quite large for a repository. As a temporary workaround you could try to set the environment variable `GOGC=20` which will make the garbage collector more aggressive. But...

The main reason is that we have to rewrite the repository index before we can delete anything. So that would mean rewriting the index twice: Once before deleting anything and...

@mirekphd The log snippet shows that restic is unable to _upload_ data but not that the backup command is unable to read certain source files.

> Yes, but the problem stems from the `/data/.minio.sys/*` folder no longer existing at source (while being backed up to the remote destination during one of the previous nightly backups):...

> The OP wrote: "I'm running the backup over a large directory hierarchy within which temporary files occasionally appear briefly. " This issue is exclusively about **warnings** in the log...

The backup command does not support any kind of user interaction. Why even use the `--exclude-cache` when you're worried about unwanted exclusions? You could instead keep track of `CACHEDIR.TAG`s by...

Which command exactly did you use create these snapshots? In a quick test I always get snapshots with a leading slash as part of the filepath. What is the output...

Since restic 0.9.6 the filename passed to `--stdin-filename` is always prefixed with a slash before storing it in a snapshot, such that paths like `database.sql` cannot end up in the...

How many exclude entries exactly do you have? I've noticed that the exclude checks take some time when you dozens of them, but that was only in the range of...

Well it would be easier (and faster) to just include all system packages in the backup. If restic preprocesses the exclude patterns then it would be possible to group ranges...