RHEL 7.2 cherry-picks #146
Merged
Conversation
This file contains 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
Related: rhbz#978266 Related: rhbz#1202877 (cherry picked from commit 491cd3e)
Related: rhbz#978266 Related: rhbz#1202877 (cherry picked from commit 792afe6)
When doing LVM/BTRFS autopart we implicitly schedule one partition on each disk as a device for LVM/BTRFS. Those implicitly scheduled partitions are requested to be at least 500 MiB big and grow if possible. That's fine and works well until we have many small disks (e.g. DASDs) and need to fit another partition (for e.g. swap) that is in combination with the 500MiB implicit partition bigger than any disk we have. Thus we need to make sure all our partition requests fit somewhere with the implicitly scheduled partitions by making the latter ones smaller or by removing them if needed. Related: rhbz#1202877 (cherry picked from commit a6d17f9) Conflicts: blivet/devices.py blivet/partitioning.py
In case of BTRFS/LVM autopartitioning we schedule one parition on every disk used for the installation to be part of the new BTRFS/LVM setup. But in case some other partition needs to be allocated (e.g. swap in case of BTRFS) we need to fit this partition to some disk together with one of the implicitly scheduled ones. In case we find out the implicitly scheduled partitions are too big to make this possible we need to make them smaller so that autopartitioning works. Resolves: rhbz#1171116 Related: rhbz#1202877 Signed-off-by: Vratislav Podzimek <vpodzime@redhat.com> (cherry picked from commit 77c5f24) Conflicts: blivet/devices.py
(Current) minimum BTRFS volume size is 256 MiB. Related: rhbz#1171116 Related: rhbz#1202877 (cherry picked from commit 16eace7) Conflicts: blivet/devices.py
|
Added the original bug IDs back. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I think it's easier to review the whole resulting diff as things move back and forth in the commits. One question -- is it correct that all the commits have 'Related: rhbz#1202877' instead of the original bugs referenced?