Comment on State of the Fin 2026-01-06 | Jellyfin
avidamoeba@lemmy.ca 2 days agoFucking hell. OK, I’ll upgrade again and wait longer. Mine’s ~15TB.
Comment on State of the Fin 2026-01-06 | Jellyfin
avidamoeba@lemmy.ca 2 days agoFucking hell. OK, I’ll upgrade again and wait longer. Mine’s ~15TB.
ragebutt@lemmy.dbzer0.com 2 days ago
Do you have music? I don’t know this for sure but I also wonder if music collections slow things down. My music collection is pretty massive (like 40% of my storage) and it’s a shitload of files to index.
Thankfully I don’t put my books in jellyfin because my ebook/manga library is also pretty massive. If the apocalypse occurs I’m set for the 2-3 days I’d have power after the end of times
avidamoeba@lemmy.ca 2 days ago
I do. It could be this:
From the release notes.
ragebutt@lemmy.dbzer0.com 2 days ago
Interesting. I will say music is the weakest point of jellyfin db. Mine is currently good but I nuked my db for the new db style in 10.11 and created a new db, mainly bc of issues within music library. But this went back to like 10.9 and were probably from me fucking around in the db manually to try and override tags. I’ve since retagged my music as it was just the easier solution (artist ft artist got me all fucked up, I hated having 900 entries for like 1 artist who did frequent collabs)
github.com/jellyfin/jellyfin/issues/15070
This is the issue thread re the very long scanning after upgrading to 10.11
avidamoeba@lemmy.ca 2 days ago
My god what a shit show.
It’s all normal though. Software development is hard and big changes mean more regressions. You do the changes when needed, then you work on squashing the bugs.
Library scan still going here. At least something is spinning because one CPU thread is pegged to 100%.