So, I'm using the usual Sonarr/Plex/Rclone setup and it's been working alright. I was having Sonarr write directly to the mount after downloads completed, but was noticing that it took a long time to move each file. My connection is 600Mbps down but only 20Mbps up, so my assumption was that the move operation was taking a while because it was uploading on the move. So I added --cache-tmp-upload-path to my mount command and that fixed the issue with the move operation. The problem I'm running into now is that once --cache-tmp-wait-time expires on one of the files in the tmp-upload-path and it starts to upload that file, every single file that is in the tmp-upload-path gets locked for modification, which causes sonarr to hang while.
Does anyone have a setup with similar limitations to mine that they are having success with?
I've just switched my setup back to not use the --cache-tmp-upload-path option because the freezing of sonarr is too frustrating. Moving the unuploaded files from the cache to the mount is going to be time consuming
Ah, thanks! I don't have much experience with filesystem in user space, but I think this makes sense to me. Just to clarify, your setup looks something like this-- Plex and sonarr are pointed to a directory from mergerfs that combines a directory that is your rclone mount with a local directory, and so whenever write operations happen, files get written to the local directory. Then you have a script that performs an rclone move operation on the local directory every night?
Awesome, thanks. How do you handle move operations what will exceed your cron frequency? moving the backlog from my --tmp-upload-path will take about a week according to my rclone progress
I keep mine on local disk because I have 6 TB and then just upload it when it gets full manually through rclone move and bwlimit it. Happily upgrading to 20 mbps upload from 10 mbps next month though.