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:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
I am using btrfs on raid1 for a few years now and no major issue.
It's a bit annoying that a system with a degraded raid doesn't boot up without manual intervention though.
Also, not sure why but I recently broke a system installation on btrfs by taking out the drive and accessing it (and writing to it) from another PC via an USB adapter. But I guess that is not a common scenario.
The whole point of RAID redundancy is uptime. The fact that btrfs doesn't boot with a degraded disk is utterly ridiculous and speaks volumes of the developers.
For my jbod array, I use ext4 on gpt partitions. Fast efficient mature.
For anything else I use ext4 on lvm thinpools.
Do you rely on snapshotting and journaling? If so backup your snapshots.
Btrfs only has issues with raid 5. Works well for raid 1 and 0. No reason to change if it works for you
I think it has more issues than just with raid 5 &6!
It is stable with raid 0,1 and 10.
Raid 5 and 6 are dangerous
Used it in development environment, well I didn't need the snapshot feature and it didn't have a straightforward swap setup, it lead to performance issues because of frequent writes to swap.
Not a big issue but annoyed me a bit.