--vfs-cache question


#1

I’m getting a lot of “Can’t open for write without O_TRUNC on existing file without --vfs-cache-mode >= writes” errors when sonarr copies files to my encrypted, cached, gdrive mount. It was my understanding that the cache backend shouldn’t be used with vfs. Is this no longer the case? If I should add it, where would I put it in my current config? My current config and mount command are below. I’m running it unraid, if it matters.

rclone mount --allow-other --allow-non-empty gdrive-crypt: /mnt/disks/gdrive-crypt

[gdrive]
type = drive
client_id =
client_secret =
token =
scope = drive

[gdrive-crypt]
type = crypt
remote = gdrive-cache:/secure
filename_encryption = standard
password =
password2 =

[gdrive-cache]
type = cache
remote = gdrive:
chunk_size = 10M
info_age = 48h
chunk_total_size = 80G
db_path = /tmp/cache-db/
db_purge = true
chunk_clean_interval = 8h0m0s
read_retries = 100
workers = 6
writes = true
tmp_upload_path = /mnt/user/cache-backend/uploads
tmp_wait_time = 1h0m0s
db_wait_time = 1m0s
chunk_path = /mnt/user/cache-backend/chunks
chunk_no_memory = true


#2

That is part of the VFS layer, not the cache backend, so if you add --vfs-cache-mode writes it should fix your problems. No need to adjust your config.