9
[Help] Media Server + *arr stack: Follow TRaSH guides or my own setup? (lemmy.ml)
submitted 1 year ago by to c/selfhost@lemmy.ml
9 comments fedilink hide all child comments
 

Hello everybody,

I want to ask for some opinions on my current setup and how I pretend to use it for my Media Server:

Current Layout

I currently use an UGREEN DXP2800 NAS running TrueNAS Scale with two 4 TB HDDs in Mirror mode. This is planned to be my "long-term storage" for backups, photos, and so on.

Additionally, I have 1 TB SSD installed in the system. I created two datasets on it: one for Docker containers and the other one for Media, following the TRaSH guides folder layout

My current plan:

My idea is to use the SSD for the torrents and the seeds, and once the file (e.g. the ~~movie ~~ Linux ISO Image) is completed, to move it to the HDDs. From there, Jellyfin would read the corresponding dataset and play the media.

The question:

The TRaSH guides puts a lot of emphasis on hardlinks and atomic moves, and that forces you to operate in one single filesystem. Is it worth it to stick to the TRaSH guide or my current setup would work just fine? What do y'all think?

Thanks in advance and happy self-hosting!

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 1 year ago

As an idea, I use an SSD as a "Default Download Directory" within qBittorrent itself, and then qB automatically moves it to a HDD when the download is fully finished. I do this because I want the write to be sequential going into my ZFS pool, since ZFS has no defragmentation capabilities.

Hardlinks are only important if you want to continue seeding the media in its original form and also have a cleaned-up/renamed copy in your Jellyfin library. If you're going to continue to seed from the HDD, it doesn't matter that the initial download is done on the SSD. The *arr stack will make the hardlink only after the download is finished.

  • permalink
  • fedilink
  • source
  • parent