Fix boot_uuid_subvolume fallback when /boot isn’t a Btrfs subvolume#415
Merged
Antynea merged 1 commit intoAntynea:masterfrom Feb 19, 2026
Merged
Conversation
Fix regression affecting systems where boot directory is not a Btrfs subvolume.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix regression on systems where /boot isn’t a Btrfs subvolume (see #414).
boot_uuid_subvolume could end up empty in that case, which makes the script pick the wrong boot path.
Now it falls back to root_uuid_subvolume when nothing is found.
I didn’t enable global pipefail to avoid unexpected side effects elsewhere.