I have a pretty annoying problem with the cache mount wrapping a simple gdrive remote (unencrypted).
I’m running rclone 1.44 in Ubuntu 16.04:
- os/arch: linux/amd64
- go version: go1.11.1
Here’s my systemd command:
/usr/bin/rclone mount cache: /mnt/cache --dir-cache-time=160h --cache-info-age=168h --allow-other --allow-non-empty --cache-chunk-size=10M --cache-workers=8 --attr-timeout=1s --syslog --umask 002 --rc --cache-tmp-upload-path /upload --cache-tmp-wait-time 2h --cache-db-path /temp/rclone --log-level INFO --cache-chunk-total-size 100G --cache-chunk-path /temp/cache-backend
ExecStop=/bin/fusermount -uz /mnt/cache
I also have dockerized sonarr/radarr with folders bound to the cache mount so all writes happen on it. The issue is that a few minutes after sonarr moves some files to the mount and plex picks them up a few items simply become unavailable. If I “ls” the cache mount directory or the media file itself it doesn’t exist yet if I do the same against the temporary upload folder it’s there. If I run “kill -SIGHUP $(pidof rclone)” and ls the cache mount directory again, the folder exists and the files are in there but this shouldn’t be a necessary step.
I recently changed the temp wait time from 30m to 2h since I was getting a relatively significant amount of 403’s and wanted to bring them down a notch (I’m using my own client and secret). I don’t remember this happening before doing that but I also updated rclone to 1.44 recently so I don’t know which one actually caused it.
Am I doing something wrong?
Help is greatly appreciated.
EDIT: Well, I think I might have fixed it by simply lowering the temp wait time to 5m. For whatever reason, I’m not seeing any 403’s now so likely the ones I was seeing were unrelated to that. I’d like to use the staging/local area instead of having to constantly upload but it looks like there are issues with that and setting a shorter wait time seems to do the trick as a workaround.