What is rclone during the last step of a copy?

Using the beta installation of rclone, I see the following output:

user@some-ip:~$ rclone copy r2:somedir/somefile.tar . --progress
Transferred:      184.866 GiB / 184.866 GiB, 100%, 0 B/s, ETA 0s
Transferred:            0 / 1, 0%
Elapsed time:     29m32.7s
Transferring:
 *                                   somefile.tar:100% /184.866Gi, 0/s, 0s

Basically, once the file has been fully downloaded, I just see a 0/s / 0B/s for many many minutes. I'm guessing what's going on is that rclone is hashing / checking, but even then I expect hashing a file to take a minute at most, and this is much longer than that. Any idea what could be taking this much time?

Edit: Running with -vvvvvv to figure it out.

Yes, it's checksumming the file as you found it.

I'm surprised the checksum takes so long, will verify with -vvvvv to see that it is indeed checksumming.

Slow disk is slow disk as no magic there unfortunately.

How about trying with --ignore-checksum?

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