Hey there,
Due to the official hubic client being near to dead, I decided recently to switch recently to rclone that seems to be a great piece of software, but I encounter issues. I spend hours and days testing the whole thing.
Here is my configuration :
- remote: hubic (about 150 Gbytes)
- rclone version: rclone v1.43.1
- OS: Ubuntu 18.04 LTS
- command:
- /usr/bin/rclone sync -vvv $SRC $DEST -L --min-age 15m --exclude-from $EXCLUDEFILE --checkers 128 --retries 1 --delete-during -n |& tee $LOGFILE
I first tried without the “-n” (dry-run) flag but I got some inconsistencies so I switched to dry run to perform extended tests.
If I run the same command several times, some large files (> 1Gbyte) are synced over and over.
In the log there is:
- 2018/10/04 11:06:53 DEBUG : path_to_the_file/DSC_3197.MOV: Modification times differ by 1h25m31.7153182s: 2017-01-09 05:09:17.2846818 +1300 NZDT, 2017-01-08 17:34:49 +0000 UTC
- […]
- 2018/10/04 11:06:54 DEBUG : path_to_the_file/DSC_3197.MOV: Returning empty Md5sum for swift large object
- 2018/10/04 11:06:54 NOTICE: path_to_the_file/DSC_3197.MOV: Not copying as --dry-run
I then checked the modification time on the remote and locally with the following commands:
- rclone lsl hubic:path_to_the_file_directory
- rclone lsl /home/path_to_the_file_directory
Both outputs regarding the file are exactly the same: - 124974528 2017-01-09 05:09:17.284681800 DSC_3197.MOV
- 124974528 2017-01-09 05:09:17.284681800 DSC_3197.MOV
I do not understand why the modtime is detected as different in the first command above and not with the lsd command.
The consequences of modtime being wrongly read for large files is that they are assumed as “dirty” since the md5sum is read to null. The file is synced over and over and at the end of the day it uses a lot of data.
What is more, I have lots of files (< 1 Gbytes) where the modtime is detected as not up to date. What is wrong. These files are not synced again but the modtime is updated.
I have about 34000 files and around 200 are detected as not up to date at each run, and they are not the same each run.
I suspect an issue on reading the modtime, as if randomly, not the modtime but the upload time was considered instead.
I don’t know if it is a bug of rclone or hubic.
Anyhow, I found a command that work well and is superfast. It uses –-update and --use-server-modtime. in dry run mode it takes only a couple of seconds to perform. I copy past it for anyone that would be interested :
/usr/bin/rclone sync -vvv $SRC $DEST -L --min-age 15m --exclude-from $EXCLUDEFILE --checkers 128 --delete-during --update --use-server-modtime |& tee $LOGFILE