Casinhas

i have exactly the same problem

Hey @alturismo, Quick update: I found other culprits, but I still haven't solved the issue of another time of day when the access time is also updated. My appdata backup plugin restarted the Plex Docker. When it came back online, the Plex library scan updated the atime on the files, which reset the cache expiry timer. This leads me to a potential solution I'd like your opinion on: What if the plugin's logic was changed to use mtime (modified time) instead of atime? The workflow would be: When the plugin moves a file to the cache, it updates its mtime to the current time (touch -m). When it detects a playback, it updates the mtime again, resetting the timer. The benefit would be that only an actual playback triggers the timer, making the system ignore background scans from Plex, Sonarr, etc. What do you think of this approach? Do you see any potential downsides for media servers like Plex with this logic? Thanks again for your work on this.

Thanks for replying. I truly understand your choice to keep the plugin simple and quick. The more you add, the more problems can arise.

Hi everyone, First of all, big thanks to the developer of the Cache Mover plugin – it's an essential part of my Unraid setup, and I really appreciate all the work that’s gone into it. I used to have the plugin working perfectly — it would track Plex access, promote recently watched files to cache, and then, after a defined expiry time, move them back to the array. Brilliant. After uninstalling and reinstalling it a few weeks later, everything seemed to work again — except for one recurring problem: The plugin still promotes media files to cache when accessed via Plex, as expected. But the expiry timer keeps getting reset, even when the file hasn’t been played again. I confirmed that Sonarr and Radarr were touching the files and updating the access time — disabling them temporarily did help. However, even with Sonarr and Radarr disabled, the issue persists. Something else is still accessing or modifying the files and resetting the expiry timer. At this point, I don’t suspect Plex itself — but it seems that even Plex’s regular library scans are now enough to reset the timer. This wasn’t happening before (at least, I don’t remember ever seeing that behaviour in the past). It almost feels like something else is also interfering, but I can’t pin down what. My Questions:In earlier versions, I had the impression that the plugin only responded to actual Plex playback access time, and ignored background scans or metadata reads from other services. Is there a way to configure the plugin to only react to real playback activity, and completely ignore background touches from apps like Radarr, Sonarr, or even Plex library scans? I’m sure I had this working just right before — but now I just can’t seem to recreate that setup. I’ve searched the forums, but honestly, the format makes it really hard to search for this specific type of behaviour — sorry if the answer is already out there and I missed it. If anyone has any insights, config tips, or a working setup they’d be willing to share, I’d truly appreciate it! Thanks again!