Progress shows more than 100 % completed on small files [superficial bug]

Suspected Bug
1

What is the problem you are having with rclone?

Small files shows a complete percentage of over 100 % when using rclone copy to Google Drive

Here is a excerpt from the progress info:

 * <redacted>/<filename>:700% /8, 0/s, -
 * <redacted>/<filename>:132% /149, 2/s, -                                                                                                                                     
 * <redacted>/<filename>700% /8, 0/s, -                                                                                                                                       
 * <redacted>/<filename>:382% /17, 0/s, -

Filesizes in this case is less than 50 kb.

What is your rclone version (output from rclone version)

rclone v1.52.0-024-g973e3d6a-fix-config-files-beta                                                                                                                                                                
- os/arch: linux/amd64                                                                                                                                                                                            
- go version: go1.14.4

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

Ubuntu Server, 64 bit. (VM)

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 <local path> <remote> --progress --transfers 16 --checkers 16 --drive-chunk-size 128M --copy-links --rc --drive-stop-on-upload-limit

I don't have a debug log atm.

2

can you post the debug log.

3

It's a known item and related to retries:

1 Like
4

We had a go at fixing that for 1.52...

It would be interesting to see a debug log to see why it didn't work in this case!

5

Ok, I'll try to recreate it.

Is the debug log enough? Because I don't think it shows the --progress console output? Or should I pipe it to a separate log file?

6

I don't think you can get anything out of the debug log. It looks like a success story of copied files and does not give any output about progress.

Anyhow, you can find them here:

Filelist: https://pastebin.com/a85X83yk
Debug.log: https://pastebin.com/4mmfZsDz
--progress Output: https://paste.drhack.net/?0fa53b7911f63173#GewZhNf1EY61BQAL7Fx4UNCTmzDzHYuYhHdwjgkr65nE (output was too big for free pastebin)

Looks like it's related to the size, all files with the same filename get's the same completed percentage.

Let me know if you want me to do more testing.

7

That is true however the paths are normally the full path so that is unambiguous.

Can you upload a .zip or .tar of the source directory for me so I can try it locally? Thanks!

8

Sent you an email with the small files compressed in a tar.gz

9

Thanks for your files. I tried to replicate it here but I haven't succeeded yet - everything stays stubbornly on 100%.

Can you do a log with -vv --stats 1s but without the -P flag - that should put the progress messages and the logs in the same file and make it a bit easier to see what is going on. Feel free to email that to me if that is easiest!

10

Yes, uploaded here:
https://drive.google.com/drive/folders/1-3r6vx9Q-wTGzugkZ0bTJAqLWzpl4EAB?usp=sharing

EDIT: Note that I'm still using the test build you made regarding the relative path.

11

Thanks. Will examine when I'm back home