Currently in my machine is ~22.75TB of porn, though I'm confident I have another drive or two with more I just need to find the time to swap some drives to verify.

I'm slowly going through it all and deleting fluff/filler content(the majority of my storage is JFF/OF content rips) from pages leaving only stuff worth watching, i.e., has some kind of pay-off.

Anything not deleted will get queued up for batch jobs I do here and there running entire folders through Handbrake for HEVC/x265 encoding.

Currently in my machine is ~22.75TB of porn, though I'm confident I have another drive or two with more I just need to find the time to swap some drives to verify.

I'm slowly going through it all and deleting fluff/filler content(the majority of my storage is JFF/OF content rips) from pages leaving only stuff worth watching, i.e., has some kind of pay-off.

Anything not deleted will get queued up for batch jobs I do here and there running entire folders through Handbrake for HEVC/x265 encoding.

So, I would assume others have been seeing this also, the problem is intermittent and seems to rarely lost longer than a couple of minutes when it happens, but, at least for myself, when using the Picture Browser or attempting to download torrents, there is a chance the connection to the database fails and spits out the following:

! "[2003] dbconn: mysql_connect: Can't connect to MySQL server on '192.168.159.53' (111)"

As someone recently dabbling in PHP/MySQL and websites/hosting more generally, so by no means any kind of authority, might I suggest stopping errors like the above from being displayed to users? That error in particular alone is innocuous enough, it just reveals an internal network IP, but that suggests a configuration that could cause other, more serious, breaches of site security.