Music Metadata High Disk Usage ?

[ydrol]

Hi, while setting up backup scripts I noticed my Jellyfin Metadata folder seemed quite large - 9G. 

I only have 121 shows and 320 movies, but I do have 2000+ albums and 28k+ songs.

Digging around it looks like there is a folder for each album, and also for many tracks that have been put in their own album. 

I have 10823 folders nested under /var/lib/docker/volumes/jellyfin-config/_data/metadata/library/**/ - each folder using approx 4kb on ext4, 

And many of the songs each have their own folder and a duplicate of the poster.jpg.


e.g. Two songs in the same album:

# ls -il /var/lib/docker/volumes/jellyfin-config/_data/metadata/library/82/8233f0991696458c4321ad6eab261bf9/
9961558 -rw-r--r-- 1 jellyfin jellyfin 16013 Dec 15 16:54 poster.jpg

ls -il /var/lib/docker/volumes/jellyfin-config/_data/metadata/library/ec/ec6508dd0ffc45785abb1df033117a0d/
10226413 -rw-r--r-- 1 jellyfin jellyfin 16013 Dec 15 16:54 poster.jpg


Is there a simple way to tidy this all up? Is it best to disable posters completely and manage this outside jellyfin.

[TheDreadPirate]

If you provide posters and album covers directly in the folder with the music, Jellyfin would not write data to the metadata directory. That has the side effect that when a client requests images it would pull them from the disk that contains your media. If your server is similar to most setups, Jellyfin's data directory is on a SSD and your media is on a HDD. Meaning that there would be extra disk I/O and the UI would be less responsive.

So there's a trade off.

I don't have access to my server at the moment. I'll need to check if this is the same situation on my server.

And your music is organized so that all songs in an album are in the same folder? And they're tagged properly and uniformly within the album?