Btrfs bigboot #72
Merged
Btrfs bigboot #72
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
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.
This PR introduces support for using the bigboot role to increase the size of a boot partition on a host using Btrfs filesystems. Previously, only hosts with LVM were supported.
Fixes #68, although I'm going to pass on the suggestion of renaming the collection.
This is mostly a rewrite of the bigboot pre-mount hook. Previously, the LVM changes using
pvmoveandpvresizewere done by the hook during the reboot. However, there is no reason these can't be done using Ansible on the running OS before the reboot. Removing the LVM bits greatly simplifies the pre-mount hook script. With this implementation, the new Btrfs changes or the old LVM changes are done by tasks included fromprep_btrfs.ymlorprep_lvm.yml, depending on if the next partition after boot is Btrfs or LVM.The new script also fixes some issues with the progress output logged by the hook. It no longer uses /dev/kmsg which proved to be troublesome if there were very long error messages. The output is now seen on the console even if the
quietkernel command line arg is set. The log outputs also can be easily seen after the reboot usingjournalctlas demonstrated in the updated README file.