Hi there, I’m getting quite a few errors like below. I’m trying to do a sync and it wont remove anything due to the errors - in a batch of around 3500 files, I’m getting 12 errors each time I run it, it seems to be the same source files having the issue each time. The source files are not being touched as far as I know (they’re old video files sitting on a network drive). I checked the last modified date on a few of them and they go back 3+ years on each.
Sorry that is not true at all. I’m running rclone on windows but the files are all stored on a freenas machine. I’m not too savvy with that stuff though. When I tried to run “lsof” I got:
Thanks for the help, you’re always so quick to reply to these… I did get a little bit more detail with 1.41 in the error but I think you can see by the error that it doesn’t really make sense… It’s change from some time in 2015 to another time in 2015. Something must be touching these files and making very minor changes to the mod time?
I’ve tried restarting the file server and the same files are getting the error.
Thanks for letting me know about the --local-no-check I can use that to get by for now but ideally it would still error (on a real error).
Having the same issue with sync from Windows NTFS to e-Open Data Storage version 7.0up57.
For example:
mod time changed from 2018-06-08 13:33:49.692955 +0200 CEST to 2018-06-08 13:33:49.6929556 +0200 CEST
I guess all these are decimal rounding discrepancies between (file) systems.
Is there any way to configure the time difference tolerance in rclone?
I was aware of the --local-no-check-updated (found it on this forum page) and it works. I was just wondering if there is a way to configure the file stamp comparare tolerance.
Ok, thanks Nick. Maybe a feature to consider in a next version. --log-level Debug emits tolerance information, it would be really nice if one could configure it.