Why can't I resume a partial upload?

Getting Help
3

Thanks for the response!

I repeated the process a few more times, this time with 10 minutes between kills, to be completely sure. Same result: B2’s usage continues to increase, now up to 3.2 GB for my 700 MB dataset.

Based on the docs, I understand restic uses content-addressable storage. I know the files aren’t changing underneath me. B2 bucket versioning is disabled (“Keep only the last version”). Shouldn’t this mean that my situation is impossible? Any re-uploaded data would overwrite a previous upload of the same data with the same hash as its filename.

I am very confident that restic is spending its time uploading, not just scanning, based on system network usage and the increasing bucket size reported from B2. The initial scan completes in about a second since I’m only backing up 276 files.

Spitballing here – restic’s docs make note of 2 directories: $TMPDIR and ~/.cache/restic.

  • $TMPDIR seems to remain empty throughout the process, from running ls a few times (or the files are unlinked immediately). However I know it’s used because I was getting errors before I set it to a file system with enough space. I verified I can write to this dir from the shell.

  • ~/.cache/restic has some directories, but only two files: CACHEDIR_TAG and $hash/version. Could this indicate a problem? I also verified I can write to this dir.

^^ may or may not be useful.

Clearly what I’m seeing should not be happening. How can I debug this further?