This repository has been archived by the owner on May 30, 2023. It is now read-only.
Support BTRFS in OEM and /usr partitions #1106
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
This was referenced Jul 14, 2021
disk_util: support compressed btrfs filesystems, use btrfs for the OEM partition
flatcar/scripts#131
Merged
pothos
force-pushed
the
kai/bootengine-verity-hashoffset
branch
3 times, most recently
from
ab9a8e7
to
cf43595
Compare
pothos
force-pushed
the
kai/bootengine-verity-hashoffset
branch
7 times, most recently
from
28089d1
to
a7bb03a
Compare
Btrfs filesystems do not support a non-standard 64k page size on arm64 when the filesystem was created by a 4k page size system. Use the default page size for arm64 to ensure compatibility with btrfs filesystems created by amd64 systems.
pothos
force-pushed
the
kai/bootengine-verity-hashoffset
branch
from
a7bb03a
to
b1b445c
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
sys-kernel/coreos-modules: use 4k pages for arm64
Btrfs filesystems do not support a non-standard 64k page size on arm64
when the filesystem was created by a 4k page size system.
Use the default page size for arm64 to ensure compatibility with
btrfs filesystems created by amd64 systems.
sys-kernel/bootengine: support btrfs /usr filesystems
Pulls in dracut: fall back to expected dm-verity hash offset flatcar/bootengine#25
coreos-base/coreos-init: support btrfs on the OEM partition
Pulls in systemd: autodetect OEM partition filesystem flatcar/init#42
sys-apps/ignition: support btrfs on the OEM partition
Pulls in internal/resource/url: support btrfs as OEM partition filesystem flatcar/ignition#21
sys-apps/seismograph: support btrfs in rootdev utility
Pulls in rootdev: support btrfs flatcar/seismograph#6
coreos-base/update_engine: support btrfs as /usr filesystem
Pulls in Support btrfs as /usr filesystem flatcar/update_engine#11
How to use/testing done
This was built and tested with the flatcar-scripts branch
kai/btrfs-usr-oemfrom flatcar/scripts#131 in http://jenkins.infra.kinvolk.io:8080/job/os/job/manifest/3029/cldsv/ where the Flatcar image that has a btrfs /usr partition and OEM partition.While the actual switch to a btrfs filesystem on the /usr partition is only possible when all changes are part of a Stable release because update-engine needs to know how to handle the new filesystem when updating, we can already do the switch for the OEM partition. The test was run first with enabling btrfs for the /usr partition, then with reverting to select the current ext2 again.