Large server-side copy in B2 fails due to 'bad byte range'

[Animosity022]

Pretty sure this is the post you want.

1.64.0 and latest beta 1.65.0 both crash on rclone crypt/sync B2 on large files

If I understand correctly, to avoid multiple network reads, rclone caches chunks in RAM. Would it be any extra pain to do the exact same caching, but to the filesystem? As we grab chunks from the network, we'd stream them directly into temp dir, and work on them there. Perhaps you're saying that unlike io.ReadSeeker, there's no common interface for writes? Let me know if this is adequate.