I'm sure it's a lot better now but everytime I see btrfs I get PTSD.

Same here. Had a production node running btrfs under heavy write load (lots of small files, frequent creates) and spent two days debugging what turned out to be filesystem-level corruption. Switched to ext4 and never looked back. The article doesn't mention what filesystem sits under Versitygw here, which seems like a pretty relevant omission for anyone thinking of replicating the setup.

▲

uroni 3 hours ago | parent | prev | next [-]

I'd worry about file create, write, then fsync performance with btrfs, but not about reliability or data-loss.

But a quick grep across versitygw tells me they don't use Sync()/fsync, so not a problem... Any data loss occurring from that is obviously not btrfs fault.

▲

__turbobrew__ 2 hours ago | parent | prev | next [-]

I hit a panic in btrfs using an ubuntu 24 LTS kernel. The trauma is still well and alive.

▲

3 hours ago | parent | prev | next [-]

[deleted]

▲

poly2it 4 hours ago | parent | prev [-]

Care to elaborate? I've heard good things about it, but am personally a ZFS user.

▲

metadat 4 hours ago | parent [-]

Years of serious corruption bugs.

▲

dundercoder 3 hours ago | parent [-]

Gluster was that for me

▲

_joel 3 hours ago | parent | next [-]

Ah, another one! Yep, also same, before ceph days at least (although I've had my own, albeit self-inflicted, nightmare there too).

▲

sigio 3 hours ago | parent | prev [-]

Yup, still get nightmares about glusterfs.... still have one customer running on it.

	▲	dundercoder 3 hours ago \| parent [-]
		I heard it got better, but we ran into the BOTF (billions of tiny files) issue around 2016. (For a genealogy startup this was a serious issue)