New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Low Storage Space after running PMM #241
Comments
added |
Does it empty trash first? It doesn't look like it does. You'd want that first so clean_bundles gets the fresh trash. There might also be a timing issue there... But it shouldn't actually break anything if there is, you just wouldn't have all the trash emptied. |
i always thought the order of doing those didn't matter but its in this order
|
i figured if it didnt do everything that day well it should finish up the next |
Yeah it wouldn't make a difference unless you decide to add something that waits until the trash finished being emptied before calling optimize and clean_bundles |
i could put in a wait but I don't think there's a way for me to know that its done all I could do is base it on time |
Sometimes it takes the trash awhile to empty if you're changing a lot of things... A wait wouldn't do much good if it couldn't be accurate 🤔 One possibility could be letting the user set an optional wait time themselves. Users with large libraries could figure out the average trash empty time and add the delay, and smaller libraries wouldn't really need it |
everything leftover will just get cleaned up the next day anyways so I don't think its really needed |
Yeah, either way having this is way better than before 👍 |
im gonna leave this open untill i merge 1.9 |
I noticed about 250GB missing today and realized it's related to old Plex metadata bundles. It would be nice if there was an option to automatically run the Optimize Database and Clean Bundles functions located in Plex Server Settings > Troubleshooting after PMM is finished.
The text was updated successfully, but these errors were encountered: