If I manually start it with just by copy pasting it in the command line, the drive mounts, if I check status (systemctl status rclone) it says running but no drive mounted.
Im new to rclone, so what im trying to achieve is use this linux VM as a NAS device on my network, so mount G Drive, and then share it thru samba and such.
I disable this and it started working on boot:
--vfs-cache-mode=full
What was weird, is that i got zero errors in the log.
The "--allow-non-empty " flag, is there because docker creates those folders before rclone mounts the drive, havent found out a way to delay docker service start until rclone is mounted.
Well, it didn't seem mounted, i would cd to the supposed mounted directory and it would be empty.
I assume you only need the header and not it checking all the directories:
In little words what's the difference between VFS and the other cache mode?
Using radarr in VFS mode, it used to import the "movie" into the cache folder, and then signaled as processed, now it seams like its uploading directly.
Is VFS better?
It really depends on what you want and what your setup is. I have a disk I use for cache to help streaming and it can work without (cache mode off) as well as it worked for many months before that new mode existed.
The rclone cache backend is deprecated and has a lot of bugs and really should not be used, but doesn't seem like you are using it anyway.
So any of those flags won't do anything unless you are using a cache remote (which you don't seem to be).
It's all workflow and what you want to setup. I use mergerfs and a local disk for all my writes and I mainly read for my rclone mount. Some people just use full mode and write directly. It all depends on what you want and how you'd like it setup. I use mergerfs because I want to use hard links.
I've shared above, which is my service file for my situation and use case. I find that works pretty well for me so there is a bit of trial and error to see what works best with your setup.
