I have a file that is in my cache-tmp-upload-path. It’s been there for about 10x longer than my cache-tmp-wait-time. I’ve tried rm from the cache mount and it says it can’t delete because the file is still being uploaded, but I can’t see any network activity from rclone that looks like an upload.
Is there a clean way to rm this file so I can add it back?
Also, does anyone know why this might have happened and how I can mitigate it in the future?
The last log message was over 4 hours ago. The delete error is from when I manually tried to rm the file. I haven’t done anything since but the file is still there.
I'm not 100% sure but I think rclone will either continue the upload after the restart or ignore the file - not sure which without checking that bit of code!
I’ve tried restarting a few times. Each time an rm says it can’t delete because of an upload, despite the fact that after the restart the upload does not start again. My guess is the cache is storing the fact the upload has been started, and so the upload doesn’t start again, nor is it removable.
Tonight I’m going to try the following steps:
stop rclone
remove file from tmp directory
start rclone
copy file to mount directory
Let me know if there’s anything else I should be checking/doing.
I’d probably stop rclone, clear out the tmp upload area, start up rclone, I’d kill -HUP to refresh the cache db. Once that builds up again, resume normal operations as it just sounds like something got caught in the middle of a stop or something along the way.
I’ve checked my tmp area and have nothing area and Sonarr/Radarr do their thing with the partials and removes and such and I have a lot of volume over the days.