I mean, the only other option was bcachefs, which might have been funny if this LLM-generated blogpost were written by the OpenClaw instance the developer has decided is sentient:

https://www.reddit.com/r/bcachefs/comments/1rblll1/the_blog_...

But no. It was btrfs.

As a side note, it's somewhat impressive that an LLM agent was able to produce a suite of custom tools that were apparently successfully used to recover some data from a corrupted btrfs array, even ad-hoc.

▲

yjftsjthsd-h 5 hours ago | parent [-]

It could be ZFS. I'd be much more surprised, but it can still have bugs.

▲

praseodym 5 hours ago | parent [-]

ZFS on Linux has had many bugs over the years, notably with ZFS-native encryption and especially sending/receiving encrypted volumes. Another issue is that using swap on ZFS is still guaranteed to hang the kernel in low memory scenarios, because ZFS needs to allocate memory to write to swap.

	▲	badgersnake 4 hours ago \| parent [-]
		The zero copy that zero copied unencrypted blocks onto encrypted file systems was genius. It’s almost like they don’t test.