Selfhosted

45553 readers

1202 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Tip: mount Jellyfin transcode directory to hard drive! (lemmy.dbzer0.com)

submitted 1 year ago by dataprolet@lemmy.dbzer0.com to c/selfhosted@lemmy.world

9 comments fedilink hide all child comments

I noticed my home servers SSD running out of space and it ended up being my Jellyfin Docker container which wasn't clearing the directory for transcodes in /var/lib/jellyfin/transcodes correctly.

I simply created a new directory on my media hard drive and bind mounted the above mentioned directory to it. Now Jellyfin got over 1 TB of free space to theoretically clutter. To prevent this I simply created a cronjob to delete old files in case Jellyfin isn't.

@daily /usr/bin/find /path/to/transcodes -mtime +1 -delete

Easy!

top 9 comments

sorted by: hot top controversial new old

[–] stuckgum@lemmy.ml 0 points 1 year ago (1 children)

Why not write to ram instead?

[–] matcha_addict@lemy.lol 0 points 1 year ago (1 children)

How much RAM would this consume?

[–] dataprolet@lemmy.dbzer0.com -1 points 1 year ago

Every transcode could need as much disk space as the size of the file you're playing. If you have a media file that's bigger than your available RAM the transcode will propably cause problems because you will run out of RAM.

[–] Novi@sh.itjust.works 0 points 1 year ago (1 children)

I transcode to ramdisk.

[–] dataprolet@lemmy.dbzer0.com -1 points 1 year ago (1 children)

I have like a dozen people using my Jellyfin and sometimes 3-4 people watch something at the same time which results in a lot of transcoding data. At the moment my transcoding directory (which is cleaned every 24 hours) is almost 8 GB big. I don't have the RAM to do this.

[–] domi@lemmy.secnd.me 0 points 1 year ago (1 children)

Starting with 10.9 you can enable segment deletion so files are cleaned up while still transcoding.

[–] dataprolet@lemmy.dbzer0.com -1 points 1 year ago

Version 10.9 is not even released, right?

[–] entropicdrift@lemmy.sdf.org 0 points 1 year ago (1 children)

Personally I have a secondary external SSD I use for my cache and transcode directories so that my transcodes aren't throttled by being read from and written to the same disk.

Also of note is that Jellyfin does have a cron job built into it to clear the transcodes directory. You can see it under Dashboard -> Scheduled Tasks -> Clean Transcode Directory. I have mine set to run every 24 hours.

[–] dataprolet@lemmy.dbzer0.com -1 points 1 year ago

Yeah, but the cleanup job doesn't seem to work reliably. I noticed because my home server ran out of disk space because the transcoding directory was over 30 GB in size.