https://fedoraproject.org/wiki/Changes/BtrfsByDefault Summary of this particular option: - Instead of a 1G ext4 volume, create a 1-2G Btrfs volume and subvolume to mount at /boot. - Desired but not a requirement of the change proposal. - Advantages: - Makes it possible to include in a btrfs-based snapshot and rollback regime along with sysroot. - Integrity checking - /boot on btrfs and btrfs subvolume/snapshot is already possible and supported by BLS and GRUB Scope of the change: use mkfs.btrfs --mixed-bg for < 5G sized volumes like this. mkfs.btrfs uses separate data and metadata block groups by default; the "soft" recommendation for "mixed block groups" is 5GB volumes or smaller.
Created attachment 1699388 [details] anaconda fails when kickstart has `part /boot --fstype btrfs` FYI I'm seeing failures when trying this in a kickstart. First attempt: part /boot --fstype=btrfs --size=1024 (see https://github.com/michel-slm/luks-kickstarts/blob/fa8348a19bd31bd3bbb7a36e5de4aee12b8c3bad/luks-btrfs-boot-minimal.ks)
Created attachment 1699390 [details] Second failure -- /boot cannot be on btrfs Second attempt: separate the `/boot` creation into two separate commands part btrfs.boot --fstype=btrfs --size=1024 btrfs /boot --label=fedora-boot btrfs.boot It now fails with ``` /boot file system cannot be of type btrfs volume ``` full KS: https://github.com/michel-slm/luks-kickstarts/blob/2da058dc38d1000a48d26cbb4401a7b6797bcf55/luks-btrfs-boot-minimal.ks
So, I see that this should be permitted in Rawhide: https://github.com/rhinstaller/anaconda/commit/72d1600a6894de1af44f6881a6ff8b6f1cc411ca Can you try from Rawhide media?
Consolidating btrfs issues for design and planning logics. The enhancement issue (use it by default, with -M option) is now found here: #7 Use /boot on Btrfs by default https://pagure.io/fedora-btrfs/project/issue/7
Oops. Renaming this to keep it as a proper bug report for the /boot on Btrfs problem in Custom and Advanced-Custom partitioning paths because it should work.
Hi Neal, it seems this should be already solved (PR merged), and this just needs confirmation. You're also the community maintainer. With "Anaconda team" as assignee, it just keeps coming up in bug triage. Is it ok if I assign the bug to you?
This is done, and if there are bugs, these should be handled separately and not in this one.