Well, unfortunately the hash problem came up in a new file (and did not appear any more for the other two above):
Line 973: 2018/04/13 12:43:58 ERROR : [file 3]: DropboxHash differ
But I think I managed to identify something: all problems occurred with files that are in a folder shared with another Dropbox user. I’ve identified that this new [file 3] with hash issues was recently modified by this user.
What I do not understand is:
Why, after all synchronized and with
rclone sync running multiple times, with modtimes and content the same in all locations, there is still a hash difference.
Why other files (a lot) that this other user changed do not present the same problem?
The following is a schematic of the configuration, to clarify:
dbhashsum - local file:
dbhashsum - Dropbox file:
dbhashsum - Dropbox BACKUP file:
Anyway, the problem does not disturb my backup (
rclone sync), since the new versions are being copied correctly.
The problem is that it generates “false positives” in the
check command, so I can not get consistent results for an automated backup verification script.
I’m sure that if I delete the file in the backup folder and reupload it, the hashes will become equal, as the other two previous files.