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:
- 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
It looks like due to the older coreutils Ubuntu 22.04 LTS is unlikely to be affected as much. So if you're on Ubuntu LTS and have not compiled it yourself, you might have dodged data corruption.
No
Nope!
OpenZFS through 2.1.13 and 2.2.x through 2.2.1 contain this bug.
This issue occurs less often in version 2.2.1, and in versions before 2.1.4, because of the default configuration in those versions.
From here
Weird. Reading the issue on GitHub I got the impression that it affects 2.2.0+.
Also I glanced something that the version of coreutils also contributes to the interaction.
E: Seems like Ubuntu LTS is unlikely to be affected a lot due to the older coreutils.
Jep, it seems like Damocles Sword was hanging above us the whole time (⊙_⊙)
At this point I think I'm just gonna wait for the patch to land in Ubuntu.