You are 100% right, I meant for the homelab as a whole. I do it for self-hosting purposes, but the journey is a hobby of mine.
So exploring more experimental technologies would be a plus for me.
Comment on Homelab upgrade - "Modern" alternatives to NFS, SSHFS?
just_another_person@lemmy.world 1 week ago
“Boring”? I’d be more interested in what works without causing problems. NFS is bulletproof.
MajorSauce@sh.itjust.works 1 week ago
just_another_person@lemmy.world 1 week ago
Most of the things you listed require some very specific constraints to even work, let alone work well. If you’re working with just a few machines, no storage array or high bandwidth networking, I’d just stick with NFS.
mitchty@lemmy.sdf.org 1 week ago
As a recently former hpc/supercomputer dork nfs scales really well. All this talk of encryption etc is weird you normally just do that at the link layer if you’re worried about security between systems. That and v4 to reduce some metadata chattiness and gtg. I’ve tried scaling ceph and s3 for latency on 100/200g links. By far NFS is easier than all the rest to scale. For a homelab? NFS and call it a day, all the clustering file systems will make you do a lot more work than just throwing hard into your nfs mount options and letting clients block io while you reboot. Which for home is probably easiest.
just_another_person@lemmy.world 1 week ago
I agree as well. No reason to not use it. If there were better ways to build an alternative, one would exist.
486@lemmy.world 1 week ago
For it to be bulletproof, it would help if it came with security built in. Kerberos is a complex mess.
Trincapinones@lemmy.dbzer0.com 1 week ago
Yeah, I’ve ended up setting up VLANS in order to not deal with encryption