On Sat, Jun 27, 2020 at 6:25 pm, Gerald B. Cox <gbcox@xxxxxx> wrote:
Making something the default is a high bar to clear. There needs to be a compelling reason why? The things listed in the proposal may be nice for some people, but the uninformed masses don't care.
There is a large list of benefits, listed at https://fedoraproject.org/wiki/Changes/BtrfsByDefault#Benefit_to_Fedora. In particular, improved detection of data corruption is definitely something that users care about, probably reason enough on its own to make btrfs default. Then Workstation#154 in particular is a very serious user experience problem that we have been trying to solve for about a year now. Under the optional optimizations section, there are the disk lifetime benefits from using zstd compression on select directories.
Another thing that is particularly troubling is I can't find where it is stated that there is a production release of BTRFS. I've seen statements that it is "testing in production" - whatever that means... and that it has been deployed on "millions of servers" - but the only statement as to code stability just says that "The Btrfs code base is under heavy development." I can't find an official statement from the project that there has ever been a production release. This is concerning to me because when I reported problems in the past I was told basically, "silly you... BTRFS should only be used in non-critical systems - if you're concerned about stability you shouldn't be running it."
Josef has provided numerous statements in this thread regarding general stability. See https://btrfs.wiki.kernel.org/index.php/Status for a detailed breakdown.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
