Do not use btrfs; it's pure shit.

Today I was hit by this 2014 issue with my 2018 kernel and userland:

Suddenly, I started getting ENOSPC errors in the middle of a package upgrade, and the system became unbootable.

df reported the partition 68% full, and btrfsck didn't find any issues. It took me *hours* to discover 'btrfs filesystem balance' and convince it to work on a full filesystem.

This isn't even the first time I have to recover a btrfs partition. Enough.

Don't get me wrong: bugs are understandable, but this behavior was well known and documented since 2014, and occurs for workloads as simple as a 20GB partition containing an arch linux desktop install (minus the home).

If the btrfs devs think that this behavior is even remotely acceptable for a Linux filesystem, I don't even want to test their code any more.

Btrfs has been around for a decade now, and it's *still* not production ready even for such a basic workload.

Sign in to participate in the conversation

Fast, secure and up-to-date instance, welcoming everyone around the world. Join us! 🌍
Up since 04/04/2017. ✅

Why should you sign up on

This instance is not focused on any theme or subject, feel free to talk about whatever you want. Although the main language is english, we accept every single language and country.

We're connected to the whole ActivityPub fediverse and we do not block any foreign instance nor user.

We do have rules, but the goal is to have responsible users.

The instance uses a powerful server to ensure speed and stability, and it has good uptime. We follow state-of-the-art security practices.

Also, we have over 300 custom emojis to unleash your meming potential!

Looking for a Kpop themed instance? Try