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
I'm confused with your answer. BTRFS is good and reliable. Ext4 gets fucked at the slightest issue.
Yes both BTRFS and Ext4 are vulnerable to unplanned powerloss when writes are in flight. Commonly knows as a write hole.
For BTRFS since it use of Copy of Write, it is more vulnerable. As metadata needs to be updated and more. Ext4 does not have CoW.
That's the only true part of this comment.
As for everything else:
Ext4 uses journaling to ensure consistency.
btrfs' CoW makes it resistant to that issue by its nature; writes go elsewhere anyways, so you can delay the "commit" until everything is truly written and only then update the metadata (using a similar scheme again).
Please read https://en.wikipedia.org/wiki/Journaling_file_system.
BTRFS is currently not Journaling
https://lore.kernel.org/linux-btrfs/[email protected]/T/#m46f1e018485e6cb2ed42602defee5963ed8c2789
Qu Wenruo did a write up on some of the edge cases. Partial write being one of them.
What you just posted concerns the experimental RAID5/6 mode which, unlike all other block group modes, did not have CoW's inherent safety.
As it stands, there is no stable RAID5/6 support in btrfs. If we're talking about non-experimental usage of btrfs, it is irrelevant.
This is where theory and practice diverge and I bet a lot of people here will essentially have the same experience I have. I will never run an Ext filesystem again, not ever as I got burned multiple times both at home/homelab and at the datacenter with Ext shenanigans. BTRFS, ZFS, XFS all far superior and more reliable.
I run BTRFS my self.
And I agree BTRFS , is superior.
Never had an issue with EXT4.
Had a problem on a NAS where BTRFS was taking "too long" for systemD to check it, so just didn't mount it... bit of config tweaking and all is well again.
I use EXT* and BTRFS where ever I can because I can manipulate it with standard tools (inc gparted).
I have 1 LVM system which was interesting, but I wouldn't do it that way in the future (used to add drives on a media PC)
And as for ZFS ... I'd say it's very similar to BTRFS, but just slightly too complex on Linux with all the licensing issues, etc. so I just can't be bothered with it.
As a throw-away comment, I'd say ZFS is used by TrusNAS (not a problem, just sayin'...) and... that's about it??
As to the OPs original question, I agree with the others here... something's not right there, but it's probably not the filesystem.