Hacker News new | ask | show | jobs
by morning_gelato 2223 days ago
> The way they are handling ZFS reminds me of the way they handled Reiser4, Tux3 and Reiserfs.

The latter file systems were trying to be upstreamed and ultimately did not succeed, I don't know of any interest or attempts at upstreaming ZFS. Their handling of ZFS reminds me how they handle any kernel module that will never be upstream, not because some file system establishment sees it as a threat.

> Basically, any filesystem not made by the filesystem establishment (and their friends) gets bullied.

What/who is the "establishment (and their friends)"?

f2fs from Samsung was added in 3.8, erofs from Huawei was added in 5.4, and exfat from Samsung was added in 5.7. Before those file systems were upstreamed I don't think many people would list Samsung and Huawei as part of the filesystem "establishment".

1 comments

>What/who is the "establishment (and their friends)"?

Maybe he thinks of Linux Foundation Platinum Members ;)

https://www.linuxfoundation.org/membership/members/

XFS is actually really good, but Linux definitely need's a check-summing COW Filesystem that's usable.

FWIW, we do have CoW on XFS, but yeah no data-checksumming other than BTRFS. Hopefully bcachefs will be the go-to option someday.
Yes true and check-summing for metadata too, but not for the data. I have bigger hopes for XFS then bcachefs (maturity and really great dev's) but hopefully not that Stratis-thing from redhat....that sound's like a terrible idea.
Writeback latency spikes and lack of data checksums is the main issue with ext4 and xfs.

Btrfs has the checksums, but is a toy.

To my knowledge, NILFS2 (by NTT) is still the best filesystem Linux has in mainline. And, ironically, practically nobody does use it.

Does NILFS2 ensure data integrity? [0] claims that it doesn't actually check data checksums, but that's from 2011...

[0] https://www.spinics.net/lists/linux-nilfs/msg01063.html