While setting up a node, I reached the storage step and had a small, confident opinion ready. Proxmox has supported btrfs as a root filesystem for years now. btrfs is in the mainline Linux kernel, ships as the default on major distributions, and runs under enormous production workloads elsewhere. So when the installer offered it, I assumed the "technology preview" label attached to it was just conservatism that nobody had gotten around to removing.
Then I read the label instead of dismissing it, went looking for why it was still there, and found that my confident opinion was wrong in an instructive way.
What I assumed
My reasoning felt airtight. The filesystem is mature. It is in the kernel everybody ships. Other platforms trust it in production. Therefore the warning is stale, a leftover from when btrfs was genuinely new, and the sensible move is to pick it and move on.
Every individual fact in that chain is true. The conclusion is still wrong, because I was reasoning about the wrong thing. "Is btrfs mature?" and "is Proxmox's btrfs integration mature?" are different questions, and I had answered the first while believing I had answered the second.
What the label actually means
Proxmox's own developers have been explicit about why the preview label persists, and it has nothing to do with doubting btrfs as a filesystem. It is about the depth of integration with the rest of the platform, compared against the filesystem the platform is genuinely built around, which is ZFS.
The gaps are in the connective tissue. Some of the storage-management features that just work on ZFS, the way the platform handles replication, certain snapshot and backup interactions, the polish of the tooling around them, are simply less complete for btrfs. The filesystem underneath is solid. The platform's assumptions and best-tested paths were built for a different filesystem, and btrfs rides in a lane that has had less traffic.
That is a completely reasonable thing to warn about, and it is invisible if you only evaluate the filesystem in isolation. The label is not saying "this might eat your data." It is saying "you are off the main road, and the main road is better maintained."
The actual lesson, which is not about filesystems
I very nearly made a storage decision for a system that holds real data based on a confident guess I had not checked, about a warning that was trying to tell me something specific. The warning was right there. I almost read past it because I already knew the answer.
That is the failure worth writing down. Being wrong about btrfs cost me nothing; almost skipping the warning because my prior was strong could have cost me a storage layout I would have lived with for years. Strong priors are exactly the ones that stop you reading. The installer was not being conservative; it was being precise, and precision aimed at a person who is sure they already understand looks identical to noise.
I picked ZFS in the end, for reasons that have nothing to do with btrfs being bad and everything to do with wanting the filesystem the platform treats as its home turf, especially for the replication and snapshot workflows my cluster leans on daily. But the decision is not the point. The point is that I made it after reading the warning and understanding it, instead of after assuming I already had.
The next time a mature tool wears a cautious label, the useful question is not "is this label out of date?" It is "what specifically is this label pointing at that I have not looked at yet?" Usually it is pointing at something real, and usually it took someone a bad week to earn the right to warn you.
