Bwlimit documentation misconception

What is the problem you are having with rclone?

I found out that the bwlimit documentation is a bit confusing sometimes.
I was happy with the extended configuration options for bwlimit.
I do not have a lot of Upload bandwidth so i used --bwlimit 3M:off (actual internet speed is 500/40).
Worked perfectly for syncs from local to remote and mounts.
But recently i used the copy command to "download" a file from remote to local but the 3M bandwidth limit was applied to it.
This means that the new bandwidth limit is based on direction between source and destination where source is you and anything flowing to destination is upload and vice versa.
But if i use rclone copy --bwlimit 3M:off remote:tmp.file local:tmp.file then from my perception i'm "downloading" a file to my local storage but rclone considers it a upload.
Just wanted to point this out and might be a good idea to update documentation accordingly

What is your rclone version (output from rclone version)

rclone v1.54.0

  • os/arch: windows/amd64
  • go version: go1.15.7

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Windows 10 x64 20H2

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

Google Drive

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

rclone copy --bwlimit 3M:off remote:tmp.file local:tmp.file

The rclone config contents with secrets removed.


A log from the command with the -vv flag


This is a bug...

Try the latest version from here - this is a pre-point release

1 Like

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