Problem copy from onedrive to onedrive

Hello I mount my drive so:
rclone mount onedrivecifrado:/ /mnt/onedr/ --allow-other

I try to copy files from one drive to onedrive and later delete i try:

rclone copy -v onedrivecifrado:/"folder1/test.txt" onedrivecifrado:/

but dosnt copy!

i try
rclone copy -v onedrivecifrado:"/folder1/test.txt" onedrivecifrado:/

but dosnt copy.

What is the correct way??.

Lot of thanks.

hi,
wne you posted, you should have been asked a set of question.
can you please answer them so we can help you?

if you are copying from remote to remote, why did you create the mount, it is not needed.
and you do not seem to be using the mount.

your command
rclone copy -v onedrivecifrado:/"folder1/test.txt" onedrivecifrado:/
is using the same remote twice, is that what you want?

what are the names of each remote?

change -v to -vv, re-run the command and post the output

What is the problem you are having with rclone?

What is your rclone version (output from rclone version)

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

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

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

A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)

Show the files to copy but after 5 minutes dosnt transfer anything.
Version is 1.51.0
I have test on windows 10 an linux ubuntu , same result.
I am using Onedrive business
I mount but I know its no need.

Two test: I have copy one file:
C:\rclone>rclone -vv copy onedrivecifrado:/"folder1/1.txt" onedrivecifrado:/folder2/
2020/02/27 18:13:12 DEBUG : rclone: Version "v1.51.0" starting with parameters ["rclone" "-vv" "copy" "onedrivecifrado:/folder1/1.txt" "onedrivecifrado:/folder2/"]
2020/02/27 18:13:13 DEBUG : Using config file from "C:\Users\pc\.config\rclone\rclone.conf"
2020/02/27 18:13:17 DEBUG : 1.txt: Size and modification time the same (differ by 0s, within tolerance 1s)
2020/02/27 18:13:17 DEBUG : 1.txt: Unchanged skipping
2020/02/27 18:13:17 INFO :
Transferred: 0 / 0 Bytes, -, 0 Bytes/s, ETA -
Checks: 1 / 1, 100%
Elapsed time: 0.0s

RESULT OK.

Second file:

rclone -vv copy onedrivecifrado:/"xxx.mkv" onedrivecifrado:/folder2/

dosnt copy:

2020/02/27 18:25:33 INFO :
Transferred: 0 / 5.819 GBytes, 0%, 0 Bytes/s, ETA -
Errors: 1 (retrying may help)
Transferred: 0 / 1, 0%
Elapsed time: 6m36.6s
Transferring:

  •             xxx.mkv:  0% /5.819G, 0/s, -
    

2020/02/27 18:25:33 ERROR : Attempt 1/3 failed with 1 errors and: async operation didn't complete after 5m0s
2020/02/27 18:25:34 DEBUG : xxx.mkv: Bad size for decrypt: file is too short to be encrypted
2020/02/27 18:25:34 DEBUG : xxx.mkv: Bad size for decrypt: file is too short to be encrypted
2020/02/27 18:25:34 DEBUG : xxx.mkv: Bad size for decrypt: file is too short to be encrypted
2020/02/27 18:25:34 DEBUG : xxx.mkv: Sizes differ (src 6247862491 vs dst 0)
2020/02/27 18:25:56 INFO :
Transferred: 0 / 5.819 GBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 1, 0%
Elapsed time: 6m58.9s

and do not copy after 5 minutes. :frowning:

lot of thanks

  1. the second command fails on both windows and linux?
  2. i would suggest that you use a log file. and post the entire log file
    https://rclone.org/docs/#log-file-file

Yes on Windows and Linux.

Could you tell me the command to put exactly?, so I will post the result...

Thanks.

try this
rclone copy onedrivecifrado:/xxx.mkv onedrivecifrado:/folder2 -vv --log-file=logfile.log

HEllo I try to move with an android program "AIS synchro" and works. But with command not.
I attach the log:

2020/02/27 19:44:05 DEBUG : rclone: Version "v1.51.0" starting with parameters ["rclone" "copy" "onedrivecifrado:/XXXXX.mkv" "onedrivecifrado:/folder2" "-vv" "--log-file=logfile.log"]
2020/02/27 19:44:05 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2020/02/27 19:44:08 DEBUG : XXXXX.mkv: Need to transfer - File not found at Destination
2020/02/27 19:45:07 INFO :
Transferred: 0 / 5.819 GBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 1, 0%
Elapsed time: 59.7s
Transferring:

  •             XXXXX.mkv:  0% /5.819G, 0/s, -
    

2020/02/27 19:46:07 INFO :
Transferred: 0 / 5.819 GBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 1, 0%
Elapsed time: 1m59.7s
Transferring:

  •             XXXXX.mkv:  0% /5.819G, 0/s, -
    

2020/02/27 19:47:07 INFO :
Transferred: 0 / 5.819 GBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 1, 0%
Elapsed time: 2m59.7s
Transferring:

  •             XXXXX.mkv:  0% /5.819G, 0/s, -
    

2020/02/27 19:48:07 INFO :
Transferred: 0 / 5.819 GBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 1, 0%
Elapsed time: 3m59.7s
Transferring:

  •             XXXXX.mkv:  0% /5.819G, 0/s, -
    

2020/02/27 19:49:07 INFO :
Transferred: 0 / 5.819 GBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 1, 0%
Elapsed time: 4m59.7s
Transferring:

  •             XXXXX.mkv:  0% /5.819G, 0/s, -
    

2020/02/27 19:49:09 ERROR : XXXXX.mkv: Failed to copy: async operation didn't complete after 5m0s
2020/02/27 19:49:09 ERROR : Attempt 1/3 failed with 1 errors and: async operation didn't complete after 5m0s
2020/02/27 19:49:10 DEBUG : XXXXX.mkv: Bad size for decrypt: file is too short to be encrypted
2020/02/27 19:49:10 DEBUG : XXXXX.mkv: Bad size for decrypt: file is too short to be encrypted
2020/02/27 19:49:10 DEBUG : XXXXX.mkv: Bad size for decrypt: file is too short to be encrypted
2020/02/27 19:49:10 DEBUG : XXXXX.mkv: Sizes differ (src 6247862491 vs dst 0)
2020/02/27 19:50:07 INFO :
Transferred: 0 / 5.819 GBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 1, 0%
Elapsed time: 5m59.1s
Transferring:

  •             XXXXX.mkv:  0% /5.819G, 0/s, -
    

2020/02/27 19:51:07 INFO :
Transferred: 0 / 5.819 GBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 1, 0%
Elapsed time: 6m59.1s
Transferring:

  •             XXXXX.mkv:  0% /5.819G, 0/s, -
    

2020/02/27 19:52:07 INFO :
Transferred: 0 / 5.819 GBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 1, 0%
Elapsed time: 7m59.1s
Transferring:

  •             XXXXX.mkv:  0% /5.819G, 0/s, -
    

2020/02/27 19:53:07 INFO :
Transferred: 0 / 5.819 GBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 1, 0%
Elapsed time: 8m59.1s
Transferring:

  •             XXXXX.mkv:  0% /5.819G, 0/s, -
    

2020/02/27 19:54:07 INFO :
Transferred: 0 / 5.819 GBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 1, 0%
Elapsed time: 9m59.1s
Transferring:

  •             XXXXX.mkv:  0% /5.819G, 0/s, -
    

2020/02/27 19:54:11 ERROR : XXXXX.mkv: Failed to copy: async operation didn't complete after 5m0s
2020/02/27 19:54:11 ERROR : Attempt 2/3 failed with 1 errors and: async operation didn't complete after 5m0s
2020/02/27 19:54:11 DEBUG : XXXXX.mkv: Bad size for decrypt: file is too short to be encrypted
2020/02/27 19:54:11 DEBUG : XXXXX.mkv: Bad size for decrypt: file is too short to be encrypted
2020/02/27 19:54:11 DEBUG : XXXXX.mkv: Bad size for decrypt: file is too short to be encrypted
2020/02/27 19:54:11 DEBUG : XXXXX.mkv: Sizes differ (src 6247862491 vs dst 0)
2020/02/27 19:55:07 INFO :
Transferred: 0 / 5.819 GBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 1, 0%
Elapsed time: 10m58.6s
Transferring:

  •             XXXXX.mkv:  0% /5.819G, 0/s, -
    

2020/02/27 19:56:07 INFO :
Transferred: 0 / 5.819 GBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 1, 0%
Elapsed time: 11m58.6s
Transferring:

  •             XXXXX.mkv:  0% /5.819G, 0/s, -
    

2020/02/27 19:57:07 INFO :
Transferred: 0 / 5.819 GBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 1, 0%
Elapsed time: 12m58.6s
Transferring:

  •             XXXXX.mkv:  0% /5.819G, 0/s, -
    

2020/02/27 19:58:07 INFO :
Transferred: 0 / 5.819 GBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 1, 0%
Elapsed time: 13m58.6s
Transferring:

  •             XXXXX.mkv:  0% /5.819G, 0/s, -
    

2020/02/27 19:59:07 INFO :
Transferred: 0 / 5.819 GBytes, 0%, 0 Bytes/s, ETA -
Transferred: 0 / 1, 0%
Elapsed time: 14m58.6s
Transferring:

  •             XXXXX.mkv:  0% /5.819G, 0/s, -
    

2020/02/27 19:59:13 ERROR : XXXXX.mkv: Failed to copy: async operation didn't complete after 5m0s
2020/02/27 19:59:13 ERROR : Attempt 3/3 failed with 1 errors and: async operation didn't complete after 5m0s
2020/02/27 19:59:13 Failed to copy: async operation didn't complete after 5m0s

I try to copy to gdrive:

rclone copy onedrivecifrado:/xxx.mkv gdrivecifrado:/ -vv and it works....

I try to copy other files and if the file is less then 5GB works!!!!!!!!!!!, i try to copy the same file from gdrive to onedrive and works, but dosnt work if I copy it from the onedrive to the same onedrive to other folder.

but... I have try to move and move works, but no copy!! strange thing any idea???.

that is an error message i have not seen.

perhaps @Animosity022 or @ncw, might have an insight?

This error means that the server side copy took longer than 5 minutes and rclone gave up waiting. It quite likely got copied eventually though - can you check?

Hello, yes I see that is 5 minutes but if you see the precess dosnt copy anything 0 bytes copied.

I have seen that if I copy a file with less than 5GB copy correct, if I copy a file bigger than 5GB dosnt copy.

You have onedrivebusiness to test it?

Thanks.

Take a look with rclone (or the web interface) to see if the file actually got copied after you get that error.

Ah!

There is nothing in the docs about a time limit

https://docs.microsoft.com/en-us/onedrive/developer/rest-api/api/driveitem_copy?view=odsp-graph-online

So I think the copy will work - can you check? If it does work I can think about how to increase the timeout.

Hello, not copy anything more than 5gb tested.
Always show 0%.
Gdrive works with the same rclone order.
Onedrive can move the file but not coy.
I see gdrive is to too too much fast coping from gdrive to the same gdrive, coping from Onedrive to the same Onedrive takes more time.

Thanks

Try increasing --timeout so add --timeout 15m to your command line - this increases the time that rclone will wait for the copy. Does that work?

According to the docs 1 & 2, it seems that it doesn't have any finite limit to the command and instead it returns a URL which can be polled asynchronously to check the status and progress.

Wouldn't that be a better solution eventually rather than increasing timeout which will not be the same every time?

That is what we do, the timeout is how long we poll the async status for.

Ah, sorry for that, missed that part in the code. Any reason not to do it indefinitely as long as its returning a valid response?

A good point... Probably just me being cautious, but as long as the endpoint is returning OK then seems reasonable!

Let's see what @akitamostodos says about whether --timeout improves things.

do not work with --timeout, same problem....

Can you post the log please?

When I did it the log were the same but with more time.

The problem I think is Onedrive and the size of the file... On gdrive works!! Is curious.

Thanks