+ F33 Btrfs By Default Test Week has concluded Test results page https://testdays.fedorainfracloud.org/events/92 Perhaps the most significant issue discovered is something of an edge case. The installer has performance issues when it encounters a Btrfs file system with many snapshots (500+ in this case). Untested, but since the handling is the same, I'd expect a similar issue with many LVM thin snapshots. https://bugzilla.redhat.com/show_bug.cgi?id=1876162#c23 --- + Subset of test day: There are two new test cases of interest that will hopefully be turned into Quick Docs: QA:Testcase partitioning custom btrfs preserve home https://fedoraproject.org/wiki/QA:Testcase_partitioning_custom_btrfs_preserve_home Draft: dual boot Fedoras - is a variation on the above test case. This is mostly leveraging BootLoaderSpec. The Btrfs part is incidental. But by using separate subvolumes for the different system roots for each Fedora, we're able to share a single Btrfs file system for much better space utilization. A future feature might be to dedup them. https://fedoraproject.org/wiki/User:Sumantrom/Draft/dualboot_f33_btrfs --- + Documentation: preliminary install-guide updates https://pagure.io/fedora-docs/install-guide/pull-request/55 https://pagure.io/fedora-docs/install-guide/pull-request/56 --- + Communication: repurposing the Fedora Btrfs wiki as a landing page is a work-in-progress https://fedoraproject.org/wiki/Btrfs --- + devel@ discussion on possibly defaulting to noatime https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/QXOM3QILEOYQ5CBSBZ5GMO5ZWQHHYZI7/#QXOM3QILEOYQ5CBSBZ5GMO5ZWQHHYZI7 -- Chris Murphy _______________________________________________ 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
