[DRAFT] build ext4 images without ext4's metadata_csum feature#1
Open
[DRAFT] build ext4 images without ext4's metadata_csum feature#1
Conversation
The "metadata_csum" feature changed in an incompatible fashion since the Linux 3.* kernel we use on `sparrow`, for example. This means that loop-mounting the ext4 on a modern Linux system and modifying it will result in a filesystem image that cannot be mounted by `sparrow`'s kernel. The error message in question is: ``` [ 156.079616](CPU:0-pid:235:dmesg) JBD2: Unrecognised features on journal [ 156.079639](CPU:0-pid:235:dmesg) EXT4-fs (mmcblk0p29): error loading journal ```
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
1 participant
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.
The "metadata_csum" feature changed in an incompatible fashion since the Linux 3.* kernel we use on
sparrow, for example. This means that loop-mounting the ext4 on a modern Linux system and modifying it will result in a filesystem image that cannot be mounted bysparrow's kernel.The error message in question is:
Marked as draft until I've actually built and tested this on
sparrow...