I think I am a bit confused about caching versus vfs cache.
Files are stored in the cloud encrypted. The remote is gdrivecm
I mount that locally using the cache backend:
[Cache]
type = cache
remote = gdrivecm:
plex_url =
plex_username =
plex_password =
chunk_size = 1m
info_age = 5h
chunk_total_size = 10G
I use this command:
rclone mount --allow-other --cache-dir /data/Library/tmp/rclonecache Cache: /mnt/gdrivecm
I then mount that locally at /mnt/Google
[Google]
type = crypt
remote = /mnt/gdrivecm/
filename_encryption = standard
password = xxx
password2= xxx
When I use this command:
rclone mount --allow-other --vfs-cache-mode writes --cache-dir /data/Library/tmp/rclonecache Google: /mnt/Google
or this command:
rclone mount --allow-other --cache-dir /data/Library/tmp/rclonecache Google: /mnt/Google
rclone ignores the --cache-dir
switch for both mounts (Cache
and Google
). The Google
mount doesn’t seem to write any cache files anywhere and the Cache
mount starts giving I/O errors after about a week. The Cache
mount writes files to ~/.cache/rclone/cache-backend
regardless of the --vfs-cache-mode
switch.
If I use --vfs-cache-dir
rclone says Error: Unkonwn flag --vfs-cache-dir
.
FYI:
$ rclone --version
rclone v1.39-001-gb412c745β
- os/arch: linux/amd64
- go version: go1.9.2
My questions are:
- Should I use a vfs-cache with the
Google
mount at all? - How do I change the cache dir location?
My goal is to have rclone keep a relatively large (like ~1 TB) disk cache either using the cache mount or the crypt mount, but to do so I have to move the cache dir to /data/Library/tmp
and I don’t understand how the cache backend and vfs-cache with the crypt backend work together.
Thanks!