My Windows 10 rclone union setup merges a local SSD drive and a remote Google Drive. The local drive is last in the union and is therefore used for writing new content to. I use rclone copy to update the Google Drive on a nightly basis with new local files and delete them soon after locally.
When copying new files to the union, the file first gets copied to the cache folder and then to the local drive, resulting in two copies of the same file. I have set a low age for the files to live inside the cache folder as to not have duplicate for a long time. I tried copying directly to the local drive but because of --dir-cache-time 72h the union does not show the new files until after that time delay.
I am using rclone mount with the union and have configured it to use --vfs-cache-mode writes. Without using --vsf writes the files get copied directly to the local drive with no caching, but I get truncate error about not using --vsf writes, which is why I have activated it. Also I want to use --vfs-read-chunk-size and --vfs-read-chunk-size-limit of to reduce API hits on the Google Drive.
- Do my rclone mount arguments look OK?
- How do I stop the duplicate files?
- What options, on Windows, do I have to merge a local drive with a remote drive in a union without having duplicate copies, local and cache, resulting in unnecessary IO usage?
- Is it safe to reduce the --dir-cache-time to 10 minutes and copy directly to the local drive?
- Is it safe to disable --vsf writes and ignore the truncate errors?
Here is my config:
type = drive
scope = drive
token = ...
type = crypt
remote = mydrive:/crypt
filename_encryption = standard
directory_name_encryption = true
password2 = ..
type = union
remotes = mydrive_crypt: C:\Users\HomeServer\Media\
Here are my mount args:
What do you clever people think about this?