rclone: local: Rclone throwing "can't copy - source file is being updated" on Glusterfs

Started on the forum and was asked to file this issue.

Have been using Rclone without issue to sync from a Gluster mounted drive to Dropbox for quite some time now, but have begun seeing the following in our logs:

ERROR : <filename>: Failed to copy: upload failed: Post https://content.dropboxapi.com/2/files/upload: can't copy - source file is being updated

This is not happening for all files, just some, and is very reproducible over many days/week for the same files.

rclone v1.40
- os/arch: linux/amd64
- go version: go1.10

Centos 7

The command being run is:

/usr/local/bin/rclone copy "/mnt/mnted_drive/" "dropbox:/<dir>/<dir>/" --max-age 3d --exclude "<term>*" >> /var/log/<log_name>

Only thing I can find in the error log is pasted above.

Along with the linked RClone forum post, I also found This

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 19 (9 by maintainers)

Commits related to this issue

local: fix spurious can't copy - source file is being updated - fixes #2206 This was caused by using == to compare time.Time values rather than time.Time.Equal. Update all the time comparisons to us... — committed to rclone/rclone by ncw 6 years ago
local: work on spurious "can't copy - source file is being updated" errors #2206 Update all the time comparisons to use time.Time.Equal instead of == Improve the logging for that error so we can see... — committed to rclone/rclone by ncw 6 years ago
local: add --local-no-check-updated to disable update checks #2206 This disables the `can't copy - source file is being updated` checks. — committed to rclone/rclone by ncw 6 years ago

Most upvoted comments

I added in a work-around with the --local-no-check-updated flag - can you give that a go?

https://beta.rclone.org/v1.40-061-gd5b2ec32/ (uploaded in 15-30 mins)

ncw on Apr 9, 2018

I’m having the same issue, the remote source is a SMB endpoint served by a Synology router and mounted on Linux via CIFS. the flag --local-no-check-updated works to solve the issue (yay!), but I’m worried it may cause some corruption in some edge cases. Or wouldn’t that be the case? What would be the possible consequences of using it?

The consequences are that rclone transfers a file which is in the process of being changed so you get a corrupted file on the destination. The next sync will sort this out though.

ncw on May 17, 2023

Any chance this can get merged in soon?

matthewmrichter on Aug 8, 2018