News for hackers. Stuff that matters.
Re:Bringing Bcachefs to Linux Mainline by techdragon on Wednesday May 18, 2022 @08:01AM (#31421687)
Since Btrfs was arguably available in the kernel too soon. Some people who should have avoided a new filesystem for lots of reasons ranging from missing features that were in the plan but not implemented yet or in the earliest days not yet stable... many of these early experimenters developed and fostered a vocal belief that Btrfs was "bad" (there's too much to sum up honestly, you could write an entire decent length blog post on the history of Btrfs, its reception and its criticism) and this group has taken a long time to accept that Btrfs may be ok now. Theres still people with the perception that its not as good or ready enough and should not be used.
Re:Bringing Bcachefs to Linux Mainline by blueflow on Wednesday May 18, 2022 @08:21AM (#31421848)
From the bcachefs homepage:

> We prioritize robustness and reliability over features and hype: we make every effort to ensure you won't lose data.

This is exactly what btrfs failed at, this is not just an issue with the code itself, but also with the developers. Why should i trust feature-oriented developers with writing my infrastructure code, where reliability and robustness are top priority?

Re:Bringing Bcachefs to Linux Mainline by viraptor on Wednesday May 18, 2022 @08:23AM (#31421875)
All this, but also two specific cases:

There's a list of features and readiness at https://btrfs.wiki.kernel.org/index.php/Status - there were people who didn't check it and used unstable features and experienced issues. This is partially on the project for not making it more explicit.

The second is that there are people who read that, see the unstable raid5/6, and are vocal about btrfs being overall broken / not ready rather than accepting that feature just not being available yet.

Re:Bringing Bcachefs to Linux Mainline by zozbot234 on Wednesday May 18, 2022 @08:26AM (#31421902)
A file system that can eat your data is broken. If a feature is not ready for public consumption, it should not be built-in in the first place.
Re:Bringing Bcachefs to Linux Mainline by viraptor on Wednesday May 18, 2022 @08:31AM (#31421950)
Then every filesystem is broken by that definition. You're setting an impossible standard given how non-specialist software is developed.

Here's a list of failures from zfs, including many kernel panics for example https://github.com/openzfs/zfs/labels/Type%3A%20Defect - is it broken and shouldn't have been released?

Re:Bringing Bcachefs to Linux Mainline by Beldin on Wednesday May 18, 2022 @10:13AM (#31423034)
Fine, let's be more nuanced: no filesystem should lose data if FAT16/FAT32/NTFS 3.1/EXT2/EXT3 wouldn't.
Re:Bringing Bcachefs to Linux Mainline by vlowther on Wednesday May 18, 2022 @10:34AM (#31423284)
well, FAT16/FAT32/EXT2 are not journalled, so making them lose data in a giant variety of ways is a trivial affair. You might want a higher bar than that.
Re:Bringing Bcachefs to Linux Mainline by Beldin on Wednesday May 18, 2022 @05:56PM (#31428150)
That's the point: if file systems that basic would NOT lose data, then it is unacceptable if another file system does.

Maybe to put it differently: new file systems should offer improvements wrt reliability for stable features of the file systems of the previous generation; regressions are unacceptable.

Re:Bringing Bcachefs to Linux Mainline by Spivak on Wednesday May 18, 2022 @10:56AM (#31423582)
Yeah, when you get down to it the opinion really boils down to "the file system is broken iff it doesn't lose data for the use-cases I personally use it for."
Re:Bringing Bcachefs to Linux Mainline by orra on Wednesday May 18, 2022 @09:11AM (#31422332)
> that feature just not being available yet.

How long are we expected to wait? It's been over a decade.

btrfs was touted as a spiritual successor to ZFS. raidz5 is a core feature of ZFS, not an incidental extra feature.

Re:Bringing Bcachefs to Linux Mainline by matheusmoreira on Wednesday May 18, 2022 @12:50PM (#31424939)
We've been waiting so long for proper software RAID support that ZFS got RAID-Z expansion before it happened. I no longer have any reason to use btrfs.
Re:Bringing Bcachefs to Linux Mainline by chasil on Wednesday May 18, 2022 @01:36PM (#31425462)
The one thing that btrfs can do that ZFS cannot is defragment. Crippling a ZFS dataset on rotational media does not appear to be at all difficult.

https://www.usenix.org/system/files/login/articles/login_sum...