Plex Credit Detection filling docke.img within /tmp

Appreciate the additional info!
Thin Provisioning - something I wasn’t familiar with but sounds pretty cool/will look into. :thinking:

I think I may end up changing over to a directory style docker setup. Shakes fist at docker
My PMS main DB/all that good stuff resides on it’s own dedicated 2TB SSD while appdata/cache (in my case where) /config live on their own 4TB SSD - 200GB reserved for docker image.

However now with the handy script + the possible larger size via directory it put my fears to bed a bit of filling up the cache drive (4TB SSD) entirely.

Just a quick bump so the topic didn’t close itself. Thanks!

Saw today in the latest beta release notes.

  • (CreditsDetection) Retry detection only a limited amount of times on failures (PM-1093)

Wondering if this might be a fix for the issue I’ve had/needed the script for cleanup?

I am going to be updating to the beta for the Push Notifications fix but will also plan on disabling script and allowing to run like normal to see if the issue of .tmp fill up occurs.

  • (Push Notifications) Used expensive DB query during playback progress notifications (PM-1166)

Thanks!

Following.

I am having the same issue, even moved from docker img to directory and found 215GB worth of space taken up by Plex Credit Detection!

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.