Selfhosted
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!
view the rest of the comments
Shit, that's a lot of storage. K.
I've lived on btrfs for years. I love the filesystem. However, RAID had been unreliable for a decade now, with no indication that it will ever be fixed; but most importantly, neither btrfs not zfs have prioritized multi-device support, and bcachefs does.
You can configure a filesystem built from an SSD, a hard drive, and a USB drive, and configure it so that writes and reads go to the SSD first, and are eventually replicated to the hard drive, and eventually eventually to the USB drive. All behind the scenes, so you're working at SSD speeds for R/W, even if the USB hasn't yet gotten all of the changes. With btrfs and zfs, you're working at the speed of the slowest device in your multi-device FS; with bcachefs, you work at the speed of the fastest.
There's a lot in there I don't know about yet, like: can it be configured s.t. the fastest is an LRU? But from what I read, it's designed very similar to L1/L2 cache and main memory.
RAID is production ready on btrfs, the only issue is the write hole on RAID 5/6. If you don't need RAID 5/6, you're fine. I use RAID 1, which is 100% production ready.
Ah, I've never considered that use case. My HDD RAID 1 array is plenty fast for what I need.
But isn't that basically what a cache drive does? It mostly caches reads, but I think it can cache writes too.
Good to know if that's your use case, but it sounds pretty niche to me.
It actually is RAID5/6 I'm looking for. Striping for speed isn't important to my, and simple redundancy at a cost of 1/2 your total capacity isn't a nice as getting 3/5 of your total capacity while having drive failure protection and redundancy.
Used to go the device mapper and LVM route, but it was a administrative nightmare for a self-hoster. I only used the commands when something went wrong, which was infrequent enough that I'd forget everything between events and need to re-learn it while worrying that something else would fail while I was fixing it. And changing distros was a nightmare. I use the btrfs command enough for other things to keep it reasonably fresh; if it could reliably do RAID5, I'd have RAID5 again instead of limping along with no RAID and relying on snapshots, backups, and long outages when drives fail.
Multi device is only niche because nothing else supports it yet. I'll bet once bcachefs becomes more standard (or, if, given the main author of the project), you'll see it a lot more. The ability to use your M.2 but have eventual consistency replication to one or more slower USB drives without performance impact will be game changing. I've been wondering whether this will be usable with network mounted shares as level-3 replication. It's a fascinating concept.