I'm just getting started on my first setup. I've got radarr, sonarr, prowlarr, jellyfin, etc running in docker and reading/writing their configs to a 4TB external drive.

I followed a guide to ensure that hardlinks would be used to save disk space.

But what happens when the current drive fills up? What is the process to scale and add more storage?

My current thought process is:

Mount a new drive
Recreate the data folder structure on the new drive
Add the path to the new drive to the jellyfin container
Update existing collections to look at the new location too
Switch (not add) the volume for the *arrs data folder to the new drive

Would that work? It would mean the *arrs no longer have access to the actual downloaded files. But does that matter?

Is there an easier, better way? Some way to abstract away the fact that there will eventually be multiple drives? So I could just add on a new drive and have the setup recognize there is more space for storage without messing with volumes or app configs?

you are viewing a single comment's thread
view the rest of the comments

[–] Karius@lemmy.ml 11 points 1 year ago (1 children)

I'm going to be adding more drives to my current basic setup soon and I think LVM is how i'm going to go, then I can just extend the filesystem across multiple drives in the future as I need

[–] SeaMauFive@lemm.ee 2 points 1 year ago (1 children)

Big thanks for this pointer. That seems like the move for me

[–] MentalEdge@sopuli.xyz 1 points 1 year ago (1 children)

LVMs can be convenient, but in my experience, they are a lot more of a headache than they're worth. But by all means give them a try. I think I just had bad luck.

But there is also nothing that stops the arrs from working across multiple drives. I use six, with content across all of them, all detected and manageable in the arrs.

[–] billygoat@catata.fish 2 points 1 year ago

This is what I do. As soon as a drive is full I create a new default root path in the arrs. Tbf, I’ve only had to do this twice so far.