I don’t like the sound of that. Sounds like bad programming? Who’s at fault? Jellyfin or the database implementation? Why would a nospace error corrupt everything. Sounds absolutely volatile. 😱
Comment on Selfhosting Sunday! What's up?
bonusss@lemmy.zip 4 weeks ago
I’ve learned a hard lesson this week. Jellyfin server OS partition run out of free space and corrupted the database. Nothing to do but reinstall. I guess this week I’ll be reviewing backups! 🤣🤣🤣
victorz@lemmy.world 4 weeks ago
Urist@lemmy.ml 4 weeks ago
They just made a blog post about the next version fixing a long standing issue with their database management. Should probably improve in the near future.
victorz@lemmy.world 4 weeks ago
Yikes. Well that’s good, at least. Progress is good.
sk@utsukta.org 4 weeks ago
oh this recently happened to me. but nothing much was lost, users were managed with SSO, files were unaffected, barely an inconvenience.victorz@lemmy.world 4 weeks ago
Watched status of the entire library was lost though right? Or no?
comrade_twisty@feddit.org 4 weeks ago
FYI from the newest release notes for 10.11.0
Jellyfin now actively checks the available free space for its configuration and data directories. If you have less than 2GB of free space in each data directory, Jellyfin now refuses to start to prevent data corruption. Additionally, checks are implemented to prevent certain path misconfigurations that are known to cause issues.jellyfin.org/posts/jellyfin-release-10.11.0/