Merge lp://staging/~oddbloke/maas-images/fix-yakkety-builds into lp://staging/maas-images
Proposed by
Dan Watkins
Status: | Merged |
---|---|
Merged at revision: | 305 |
Proposed branch: | lp://staging/~oddbloke/maas-images/fix-yakkety-builds |
Merge into: | lp://staging/maas-images |
Diff against target: |
76 lines (+30/-9) 1 file modified
bin/maas-cloudimg2eph2 (+30/-9) |
To merge this branch: | bzr merge lp://staging/~oddbloke/maas-images/fix-yakkety-builds |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Scott Moser (community) | Needs Fixing | ||
Review via email:
|
Commit message
Disable metadata_csum when creating ext4 filesystems
In yakkety, we have sync'd an e2fsprogs version that supports metadata
checksumming in ext4 and enables the feature by default. Unfortunately,
some Launchpad buildds (specifically those for armhf and one for powerpc)
are running on a kernel that is too old to support this, which means an
unusable ext4 partition is created. To work around this issue, we disable
the metadata_csum option when we create an ext4 filesystem.
The Launchpad team are working to upgrade the offending build hosts, so we
should be able to back this change out before yakkety releases.
To post a comment you must log in.
$ lsb_release -sc
xenial
$ truncate --size 1G foo; mkfs.ext4 -O ^metadata_csum -F foo -L cloudimg-rootfs; echo $?
mke2fs 1.42.13 (17-May-2015)
Invalid filesystem option set: ^metadata_csum
1