this post was submitted on 23 Mar 2025
31 points (89.7% liked)

Selfhosted

44937 readers
577 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Hey all, I've got ZFS pool created and just create a VM drive in that pool like normal, then Jellyfin just has that drive mounted. I think I'm losing the best parts of ZFS through this manner.

How should I set this up properly? Create a media pool or something and have VMs accessing the pool directly?

you are viewing a single comment's thread
view the rest of the comments
[–] Xanza@lemm.ee 12 points 2 days ago* (last edited 2 days ago) (21 children)

So if you're going through the trouble of setting up proxmox, I would setup the majority of the storage in a ZFS pool for a TrueNAS SMB share/NFS share. Then create a small container just to host jellyfin and jellyfin's cache--maybe commit 10GB of storage to it--really depends on how big your media library is. Mine is about 5TB and cache, metadata, and other misc things take up about 8GB.

Setting up your share is enough for jellyfin. Since the media and jellyfin are stored on the same metal, additional latency will be sub 100ms. Create a library in Jellyfin and set it to the share; Movies: \\nas\Movies, TV: \\nas\TV, etc.

Works flawlessly and would have more utility than allocating the entirety of your storage to your jellyfin container because it functions as a normal NAS. I've been running with a setup like this for a while and it works great.

[–] Matty_r@programming.dev 2 points 2 days ago (4 children)

Are you suggesting creating a TrueNAS VM? Wouldn't that be the same as what I'm doing now with creating an image in the ZFS pool?

[–] suicidaleggroll@lemm.ee 2 points 2 days ago

I would separate the media and the Jellyfin image into different pools. Media would be a normal ZFS pool full of media files that gets mounted into any VM that needs it, like Jellyfin, sonarr, radarr, qbittorrent, etc. (preferably read-only mounted in Jellyfin if you’re going to expose Jellyfin to the internet).

load more comments (3 replies)
load more comments (19 replies)