I never saw a cache that first copies unchanged data for some operation.
I would have suspected that it will mostly be used for downloading files - so that they are complete before writing them back to the target location or offering them in the mounted file system. So that they can then ne stably accessed.
If disabling is the solution here, I would need to partition any work into "pure upload" and "regular access" to that the cache will only be used for the latter.
But this is really unexpected behaviour, to be honest.
With rclone you can NOT have cache only for reads.
If you do write to your remote I would strongly recommend to use VFS full caching mode. It will be not only snappier behaviour but also greater compatibility with your other programs. Without write cache your mount won't behave like normal filesystem and some programs simply will refuse to work (in case you write to files in your mount).
BTW. You are the first person asking for cache only for read operations. I still can not fully understand why:) It is not really logical. As I do not see what benefits would be.
Yes, I was reading the different options now in detail.
It seems, the best option would be "writes" ... that seems to be what I thought to be the "default" behaviour of a cache.
Thanks a bunch!
But I did not ask for a "read cache" - I am just accessing a remote that is basically empty and I am in the process of uploading stuff. There would no caching be needed, which can be done with the 'writes" option, if I understood that correctly.
For initial upload I would use rclone copy/move/sync and not mount. Not only faster than mount but also gives you some visibility what is going on and stats.
