Metadata keeps filling up /var/ partition

[Huecuva]

I'm running Jellyfin on a headless Debian VM in Proxmox and it has a separate 4GB /var partition. Unfortunately, it seems that Jellyfin keeps filling it up with /var/lilb/jellyfin/metadata. I've restored backups of my server several times to points prior to the partition becoming full in attempts to temporarily mitigate this problem, but...as I stated, it is temporary and quickly becoming annoying. Is there some way to solve this problem permanently? A way to perhaps migrate the metadata to a different partition or something?

[Efficient_Good_5784]

Do you have trickplay generation enabled for any libraries? That's the location where the trickplay files are stored.

Also, chapter images are also stored there too.

[Huecuva]

I don't know what trickplay is. How do I check whether it's enabled? I currently can't even get to the Jellyfin webgui as the /var partition is 100% full. I'm in the process of again restoring an older backup of the server in an effort to gain access to the webgui and do whatever configuration I need to do.

EDIT: After some googling, it seems that Trickplay is disabled by default. I didn't even know it was a thing so I have definitely never enabled it. However, chapter images may be contributing to my problem. How do I a) purge existing chapter images and b) store them elsewhere?

[TheDreadPirate]

You could symlink /var/lib/jellyfin to another, larger, partition.

[Huecuva]

How would I go about that?

EDIT: I think I figured out how to create the symlink itself: sudo ln -s ~/Storage/var /var/lib/jellyfin. However, the original /var directory is still really full. Does everything get moved automatically and the du command just includes what's in the symlinked directory or is there more to be done?

[Efficient_Good_5784]

On the topic of space, 4GB is a bit small for your needs.

From what I understand, your server is acting normally and this doesn't sound like a bug.
The only real solution is for you to either shrink the size of your libraries (delete media), or increase the size of the /var partition.
Or figure out how to get the symlinks to work.

It will grow as your library grows, there's no way around that.

[Huecuva]

Yeah, I've already symlinked the /var/lib/jellyfin directory to a directory on my NAS which has ample space (the NAS is the same server as the Jellyfin host, just a much bigger attached drive. The same drive where all my media is stored). I'm just wonder now if more needs to be done since /var still seems to be pretty big. Does the du command include what's in the symlinked directory and everything just gets moved automatically when the symlink is created or is there something else I need to do after creating the symlink?

[Efficient_Good_5784]

Yeah, I've already symlinked the /var/lib/jellyfin directory to a directory on my NAS which has ample space (the NAS is the same server as the Jellyfin host, just a much bigger attached drive. The same drive where all my media is stored). I'm just wonder now if more needs to be done since /var still seems to be pretty big. Does the du command include what's in the symlinked directory and everything just gets moved automatically when the symlink is created or is there something else I need to do after creating the symlink?

Try reading this and see if it helps answer your question: https://unix.stackexchange.com/questions...disk-usage

[TheDreadPirate]

Having /var/lib/jellyfin on a NAS is not ideal since that also means that database queries, which have a lot of small and random accesses, would massively slow down Jellyfin's responsiveness.

[Huecuva]

The NAS is not actually network attached to the jellyfin server. ~/Storage is a mounted 18TB RAIDZ attached to the server itself that is hosting jellyfin. It is only NAS to the rest of the LAN. Is that still not good? I suppose I could make a directory in ~/ which is 45GB and symlink to that instead. Would that be better?

Regarding the link Efficient_Good posted above: after messing around with du a bit, it seems like when I du -L /var it now says it's 6GB and du -L ~/Storage/var is 3GB and du /var is 3GB. so it looks like I might have duplicate metadata after simply creating the symlink, since I copied everything from /var/lib/jellyfin/ to ~/Storage/var before creating the symlink. Do I not need to copy? Should I copy first, then delete from /var before creating the symlink? I'm not sure how to fix this. Though, I think if I create a directory in ~/ I can start over.