Is it possible that a failed rclone copy results in a 0 byte output file?
Referring to https://github.com/cjnaz/rclonesync-V2/issues/56, there appear to be cases where if the transfer is terminated during a file copy that a 0 byte (or perhaps incomplete) file gets created at the destination, which is probably data loss for a bi-directional sync.
The transfer may fail for several reasons, including.. the internet connection drops, the client machine is hibernated, crashes or is rebooted.
When a copy (or a sync) is in process, is a temporary file created at the destination, and renamed/moved to the final output name at the end of the successful transfer?
If so, are all remotes as destinations supported for this behavior?
Is a transfer to a local filesystem supported for this behavior?
Are there any rclone switches related to this behavior?
If this behavior is not supported, what are the blocking reasons?
What is your rclone version (output from rclone version)
Which OS you are using and how many bits (eg Windows 7, 64 bit)
Centos 7.8 64b and Windows 10 64b
Which cloud storage system are you using? (eg Google Drive)
Google Drive, Local, Owncloud, ...
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone copy GDrive:fileXYZ <localdrivepath>
rclone copy <localdrivepath> GDrive:fileXYZ
For now I'll look into implementing temp file naming on local/sftp/ftp on Path1. I use an rclone sync Path1 Path2 as the final step, so would need rclone built in support if a local/sftp/ftp target is on Path2. I'll put in a feature request on github.