I want to use rclone mount and cache directory listing and files. I tried to use : --dir-cache-time 1000h --poll-interval 15s --cache-dir="cache" but it seems it does not use the cache-dir at all, it just cache on memory.
I need to use VFS cache option for that ?
Also, i don't want to wear my ssd, can i use a ramdisk to store vfs file caching data but keep directory listing / file metadata to a real ssd directory ?
No. There is no split different cache data option. You can have all cache in memory or on disk. To use memory you have to create RAM disk and point cache there. But IMO this is waste of RAM unless you have very demanding workflow and plenty of memory
I tried something like
.\rclone.exe mount remote:/ localdir --dir-cache-time 1000h --poll-interval 15s --cache-dir="E:\cache-merge" --read-only --vfs-cache-mode full --vfs-cache-max-size 50G --buffer-size 100M --bind 192.168.1.124
And upon closing, it don't feel like directory listing were saved, i did a recursive list of my files with ls . -r but my vfs and vfsMeta folders are still empty.
So i'm not sure that directory listing are saved outside of memory, or maybe i'm missing an option ?
Ok, do you have a link to this feature so i can support it ?
It's a shame to have to do a full listing of your directory each time you relaunch rclone.
Also, i read this tip, i don't know if its still up to date :
Use : \rclone.exe mount s-merge:/ mountmerge --rc --attr-timeout 1000h --dir-cache-time 1000h --poll-interval 15s --cache-dir="J:" --read-only --vfs-cache-mode full --vfs-cache-max-size 8G --buffer-size 100M --bind 192.168.1.124 --rc-user=time --rc-pass=xxx --rc-web-gui
And then : .\rclone rc vfs/refresh --user time --pass xxx
To trigger a fast-list search and preload cache dir.
About VFS caching now, in VFS full mode, does the cache have to be bigger than files used ? Like if i set it to 10GB of ramdisk, what happen if i tried to open a heavy video file ?
yes but not all remotes support fast-list - it will work regardless and warm up all cache
Yes - size of cache can exceed what you set in vfs-cache-max-size, so it can get as big as your biggest file. As per docs:
If using --vfs-cache-max-size note that the cache may exceed this size for two reasons. Firstly because it is only checked every --vfs-cache-poll-interval. Secondly because open files cannot be evicted from the cache.