#996 [btrfs-progs] btrfs-progs-6.0 is available | rhbz#2094075
Closed by blockerbot. Opened by blockerbot.

Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2094075 **
Information from BlockerBugs App:
2094075

Current vote summary

Commented but haven't voted yet: adamwill, gui1ty, kparal

The votes have been last counted at 2022-11-01 09:22 UTC and the last processed comment was #comment-823726

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review
A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)


What does "for parity" mean, exactly? What "parity" is there between btrfs-progs and the kernel?

What does "for parity" mean, exactly? What "parity" is there between btrfs-progs and the kernel?

It means that btrfs-progs 6.0 configures btrfs with features from kernel 6.0 when they are used together. This can mean using the correct feature defaults, among other things. Generally btrfs-progs and the kernel are released in lockstep upstream for this reason.

Is the only consumer of btrfs-progs on the release media the installer? I'm not thinking of anything else. The Btrfs commands it uses are: mkfs.btrfs, btrfs subvolume create, btrfs subvolume delete, and maybe btrfs subvolume list. There are a few mkfs fixes in btrfs-progs 6.0, but we aren't affected. In this sense there's very low risk of taking 6.0, but no needed functionality or fixes in 5.19.1. Also, Rawhide had 6.0 series in it with btrfs-progs 5.19.1 for a while and didn't hit anything weird as far as I know.

https://btrfs.readthedocs.io/en/latest/CHANGES.html

FinalFE 0

@chrismurphy We never shipped 5.19 for Fedora 37. This is an upgrade over btrfs-progs 5.18. It's way more significant since there are fixes from 5.19 rolled up into it (including mkfs fixes for zoned devices and performance improvements for creating large filesystems).

Ohhh yeah. There are lots of other fixes between those versions, so that makes me a weak +1.

While it is true that btrfs-progs can be updated in the Live environment, (a) it's a bit much to ask users to do a progs update before running the installer (b) it can't be updated on DVD and netinstaller media. Also, mismatch between progs and kernel versions is expected to be self-adjusting, i.e. I wouldn't tie them together when deciding this exception. btrfs-progs 6.0 is fine to use with kernel 5.19 series too. I can't even tell you when I last saw a bug related to either older or newer progs, compared to the kernel version.

FinalFE +1

Hmm. Depends on the impact for QA in testing this update and if any of the proposed fixes are actually affecting the installation process. I will keep my vote for the meeting.

Accepted as a freeze exception during a blocker review meeting:
https://meetbot.fedoraproject.org/fedora-blocker-review/2022-10-31/f37-blocker-review.2022-10-31-16.00.log.html

AGREED AcceptedFinalFreezeException

The following votes have been closed:

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

Release F37 is no longer tracked by BlockerBugs, closing this ticket.

Log in to comment on this ticket.

Metadata