Rclone sync to Backblaze B2 fails with ~7 GB file using the --backup-dir option

What is the problem you are having with rclone?

I am syncing a ~7 GB file to an empty Backblaze B2 bucket from my PC with the "rclone sync" command. It works fine on the initial sync. Problem is when I update the file and rerun the sync, rclone is not successful when trying to copy the original file to the backup location. Tries over and over to copy the first couple chunks, but constantly gets errors from the Backblaze B2 API.

I am using the latest rclone docker image (v1.60.1).

Run the command 'rclone version' and share the full output of the command.

rclone v1.60.1
- os/version: alpine 3.16.3 (64 bit)
- os/kernel: 5.10.28-Unraid (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.19.3
- go/linking: static
- go/tags: none

Which cloud storage system are you using? (eg Google Drive)

Backblaze B2

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone: Version "v1.60.1" starting with parameters ["rclone" "--fast-list" "-vv" "sync" "/backup" "BackupsBackblazeB2-crypt:/current" "--backup-dir" "BackupsBackblazeB2-crypt:/old"]

The rclone config contents with secrets removed.

type = b2
account = XXX
key = YYY
hard_delete = true

type = crypt
remote = BackupsBackblazeB2:ZZZ
filename_encryption = standard
directory_name_encryption = true
password = 111
password2 = 222

A log from the command with the -vv flag

2022/11/26 22:50:01 DEBUG : abc: Error copying chunk 2 (retry=true): Post "https://api002.backblazeb2.com/b2api/v1/b2_copy_part": EOF: &url.Error{Op:"Post", URL:"https://api002.backbla
zeb2.com/b2api/v1/b2_copy_part", Err:(*errors.errorString)(0xc0000a8120)}
2022/11/26 22:50:01 DEBUG : pacer: low level retry 1/10 (error Post "https://api002.backblazeb2.com/b2api/v1/b2_copy_part": EOF)
2022/11/26 22:50:01 DEBUG : pacer: Rate limited, increasing sleep to 20ms

The above error repeats over and over for chunk 1 and 2. I see in the Backblaze B2 console that unfinished large files come and go under the backup folder. Thoughts?

This could be a bug.

Can you find the smallest file that you can reproduce the problem with and give me instructions on how to reproduce please and I'll investigate further.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.