Is rclone moveto safe when hitting the Google upload limit and using --drive-stop-on-upload-limit?

What is the problem you are having with rclone?

I may have lost some data when I was using rclone moveto without the --drive-stop-on-upload-limit, hit the quota and I terminated the rclone process with Ctr-C. It is difficult for me to reproduce, so I am asking if using rclone moveto --drive-stop-on-upload-limit will simply fail and the local file remains intact or if I am risking losing the source file even if the upload fails due to exceeding the upload quota.

Or should I use some kind of wrapper script that uploads, then checks and only deletes if uploaded file has matching size on the cloud drive? (any hints welcome, if someone already did this)

What is your rclone version (output from rclone version)


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

macos, debian

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 moveto --drive-stop-on-upload-limit ...

Moveto like copy or move would fail if you get an error and not upload therefore not deleting the file.

1 Like

Meanwhile I was able to verify it:

Not deleting source as copy failed: googleapi: Error 403: User rate limit exceeded. ...

Great! and thanks for your help.

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