Selfhosted

42055 readers

544 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Homelab upgrade - "Modern" alternatives to NFS, SSHFS? (sh.itjust.works)

submitted 1 day ago* (last edited 1 day ago) by MajorSauce@sh.itjust.works to c/selfhosted@lemmy.world

64 comments fedilink hide all child comments

Hi all!

I will soon acquire a pretty beefy unit compared to my current setup (3 node server with each 16C, 512G RAM and 32T Storage).

Currently I run TrueNAS and Proxmox on bare metal and most of my storage is made available to apps via SSHFS or NFS.

I recently started looking for "modern" distributed filesystems and found some interesting S3-like/compatible projects.

To name a few:

MinIO
SeaweedFS
Garage
GlusterFS

I like the idea of abstracting the filesystem to allow me to move data around, play with redundancy and balancing, etc.

My most important services are:

Plex (Media management/sharing)
Stash (Like Plex 🙃)
Nextcloud
Caddy with Adguard Home and Unbound DNS
Most of the Arr suite
Git, Wiki, File/Link sharing services

As you can see, a lot of download/streaming/torrenting of files accross services. Smaller services are on a Docker VM on Proxmox.

Currently the setup is messy due to the organic evolution of my setup, but since I will upgrade on brand new metal, I was looking for suggestions on the pillars.

So far, I am considering installing a Proxmox cluster with the 3 nodes and host VMs for the heavy stuff and a Docker VM.

How do you see the file storage portion? Should I try a full/partial plunge info S3-compatible object storage? What architecture/tech would be interesting to experiment with?

Or should I stick with tried-and-true, boring solutions like NFS Shares?

Thank you for your suggestions!

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

[–] Appoxo@lemmy.dbzer0.com 2 points 21 hours ago* (last edited 21 hours ago) (1 children)

Thanks for digging this "shallow" (lol. What you dug up is equal to my senior technician explaining the full tech stack of a client).
Anyway, I host the system disk on local disk and NFS storage acts as the mass storage for my VMs like my media server for jellyfin).
And I also do daily backups with Veeam Backup and Replication of both my most important files of my media server and the important VMs.
So in case of a data failure it should be more or less fine.

Wouldnt the sync option also confirm that every write also arrived on the disk?
Because I did mount the NFS (Storage host: TrueNAS, Hypervisor: Proxmox) in sync mode.

[–] tal@lemmy.today 2 points 16 hours ago* (last edited 16 hours ago)

Wouldnt the sync option also confirm that every write also arrived on the disk?

If you're mounting with the NFS sync option, that'll avoid the "wait until close and probably reorder writes at the NFS layer" issue I mentioned, so that'd address one of the two issues, and the one that's specific to NFS.

That'll force each write to go, in order, to the NFS server, which I'd expect would avoid problems with the network connection being lost while flushing deferred writes. I don't think that it actually forces it to nonvolatile storage on the server at that time, so if the server loses power, that could still be an issue, but that's the same problem one would get when running with a local filesystem image with the "less-safe" options for qemu and the client machine loses power.