Remix.run Logo
nerdjon 3 days ago

It is interesting seeing this article come up since just yesterday I setup longhorn in my homelab cluster needing better performance for some tasks than NFS was providing so I setup a raid on my r630 and tried it out.

So far things are running well but I can't shake this fear that I am in for a rude awakening and I loose everything. I backups but the recovery will be painful if I have to do it.

I will have to take a look at rook since I am not quite committed enough yet (only moved over 2 things) to switch.

master_crab 3 days ago | parent | next [-]

If the information is truly important push it off to a database or NAS. I use rook at home but really only for long lived app data (config files, etc). Anything truly important (media, files, etc) is served from an NFS attached to the cluster.

cortesoft 3 days ago | parent | prev [-]

I have a small 4 node home cluster, and longhorn works great... on smaller volumes.

I have a 15TB volume for video storage, and it can't complete any replica rebuilds. It always fails at some point and then tries to restart.

nerdjon 3 days ago | parent [-]

That is good to know then, I am really just using this for smaller volumes. My media is sitting at about the same size yours is and instead of using PVC's I just have it mounting a straight NFS share specifically for that to avoid any issues there.

I think I am likely keeping most of my storage just setup with a storage class that uses my NFS as storage. But longhorn will be used for the things that need to be faster like the databases. I moved jellyfin over to Longhorn and it went from being borderline unusable while metadata was grabbed to actually working well.

I can't imagine my biggest volume being more than 100gb, and even that is likely a major over estimation on my part.