2024-07-23, 09:39 PM
(This post was last modified: 2024-07-23, 09:40 PM by TheDreadPirate. Edited 1 time in total.)
What version of Jellyfin are you running? 10.8.X? You have to be if delete segments is not an available option.
2-3GB per minute is pretty normal for hardware accelerated transcodes or remuxes.
Keep in mind that /var/lib/jellyfin also contains all your metadata. It is where images are stored (assuming you aren't saving them in the media directory) as well as the database. My /var/lib/jellyfin directory was 4GB before I enabled trickplays. Now it is 17GB.
So if you've added a lot of new media, /var/lib/jellyfin will slowly continue to grow as it stores more images. Which means less room for transcodes.
Also, if you are adding higher quality media, the transcodes will also be larger. Or if your clients were direct playing before, but your new media uses codecs that your client can't direct play so it now has to transcode.
A lot of possibilities.
But if you don't want to increase the volume size, #3 is your best bet. Move the transcode path to another volume.
2-3GB per minute is pretty normal for hardware accelerated transcodes or remuxes.
Keep in mind that /var/lib/jellyfin also contains all your metadata. It is where images are stored (assuming you aren't saving them in the media directory) as well as the database. My /var/lib/jellyfin directory was 4GB before I enabled trickplays. Now it is 17GB.
So if you've added a lot of new media, /var/lib/jellyfin will slowly continue to grow as it stores more images. Which means less room for transcodes.
Also, if you are adding higher quality media, the transcodes will also be larger. Or if your clients were direct playing before, but your new media uses codecs that your client can't direct play so it now has to transcode.
A lot of possibilities.
But if you don't want to increase the volume size, #3 is your best bet. Move the transcode path to another volume.