#2538 F34 Change: Enable btrfs transparent zstd compression by default
Closed: Accepted 9 months ago by sgallagh. Opened 9 months ago by bcotton.

On variants using btrfs as the default filesystem, enable transparent compression using zstd. Compression saves space and can significantly increase the lifespan of flash-based media by reducing write amplification. It can also increase read and write performance.


+1 assuming that change page will be updated to mention that /boot is not going to be compressed (or opposite but with implementing proper support in grub2).

+1 assuming that change page will be updated to mention that /boot is not going to be compressed (or opposite but with implementing proper support in grub2).

@ignatenkobrain /boot is currently still a separate ext4 partition; on BIOS systems grubenv is stored there (it's on /boot/EFI on EFI systems) so having /boot on btrfs will break anything that relies on GRUB being able to modify its environment during execution (e.g. the hidden GRUB menu in Fedora Workstation).

We were initially going to propose a separate Change Proposal to get grubenv moved to a place that's consistently writable, but Javier is currently proposing this for F34: https://fedoraproject.org/wiki/Changes/UnifyGrubConfig so it's better to wait for that; I have a draft of the /boot on btrfs proposal that I will readjust based on how UnifyGrubConfig is received and plan to target for F35 (Javier will co-own it).

I can update the compression proposal to mention /boot on btrfs to be out of scope.

/boot is currently still a separate ext4 partition

However, it is possible to install /boot on btrfs via advanced partitioning... And we need to make sure that it does not get compresset so that after installation system won't boot.

I can update the compression proposal to mention /boot on btrfs to be out of scope.

Yes, please. And make sure to test aforementioned scenario so that we avoid unnecessary breakage.

/boot is currently still a separate ext4 partition

However, it is possible to install /boot on btrfs via advanced partitioning... And we need to make sure that it does not get compresset so that after installation system won't boot.

I can update the compression proposal to mention /boot on btrfs to be out of scope.

Yes, please. And make sure to test aforementioned scenario so that we avoid unnecessary breakage.

Zstd compression is supported by GRUB, so I wouldn't worry about it.

/boot is currently still a separate ext4 partition

However, it is possible to install /boot on btrfs via advanced partitioning... And we need to make sure that it does not get compresset so that after installation system won't boot.

I can update the compression proposal to mention /boot on btrfs to be out of scope.

Yes, please. And make sure to test aforementioned scenario so that we avoid unnecessary breakage.

Zstd compression is supported by GRUB, so I wouldn't worry about it.

Will update to include these. Thanks!

/boot is currently still a separate ext4 partition

However, it is possible to install /boot on btrfs via advanced partitioning... And we need to make sure that it does not get compresset so that after installation system won't boot.

I can update the compression proposal to mention /boot on btrfs to be out of scope.

Yes, please. And make sure to test aforementioned scenario so that we avoid unnecessary breakage.

Zstd compression is supported by GRUB, so I wouldn't worry about it.

Will update to include these. Thanks!

updated by adding this section: https://fedoraproject.org/wiki/Changes/BtrfsTransparentCompression#Will_.2Fboot_be_compressed.3F

After a week, I count the vote as (+8,0,-0). Processing the change as accepted.

Metadata Update from @bcotton:
- Issue tagged with: pending announcement

9 months ago

Metadata Update from @sgallagh:
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

9 months ago

Login to comment on this ticket.

Metadata