January 8, 20224 yr Hi, Happy new year everyone! I've been thinking the last few days about the amount of apps/containers/VM's/etc. that can put excess writes on a given cache drive in Unraid, and what the real solution to it is, beyond accepting a loss of a drive. To be clear, I am aware that this isn't an Unraid problem per-say (although the loop2 bug contributes, with its own workarounds), so I'm using Unraid here as an example as that's what I'm running at home. Lets use stats and analysis through Grafana as an example - Standard config, influx and Prometheus/similar pulling stats from fairly standard home-lab systems, like UniFi, Unraid, HomeAssistant, etc. All useful data that can help draw some pretty graphs - but not without adding more undue wear on a given SSD. How are people actually handling this long term? Accepting the loss of a SSD? Shipping the log writing off of Unraid to something else (and moving the problem there?)? HDD usage? Logging the databases to RAM where possible, flushing every hour or so? Something else? How are we all handling this problem? Thanks!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.