FDE image fails to run e2fsck

Bug #2025339 reported by Jean-Baptiste Lallement
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
e2fsprogs (Ubuntu)
Fix Released
Undecided
Unassigned
Jammy
Confirmed
Undecided
Unassigned

Bug Description

After installation of the FDE image, the system fails to boot due to e2fsck failing with:

Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported feature(s): FEATURE_C12

----

this means that Jammy fsck fails against mantic created ext4 which is not great

Seems this is orphan_file feature / orphan_present

Also need to check if grub2 supports this as it is RO_INCOMPAT feature.

description: updated
description: updated
description: updated
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Given new incompatible RO and RW features in ext4 that v5.15 kernels support, imho we should SRU backport of e2fsprogs on HWE grounds.

Revision history for this message
Alfonso Sanchez-Beato (alfonsosanchezbeato) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in e2fsprogs (Ubuntu Jammy):
status: New → Confirmed
Changed in e2fsprogs (Ubuntu):
status: New → Confirmed
Revision history for this message
Julian Andres Klode (juliank) wrote (last edit ):

Newer releases of Ubuntu can always start making use of new file system feature flags. Looking at all currently supported releases (whether standard or ESM), we have never SRUed e2fsprogs before, it only ever received security updates, so I'd be inclined to not do a backport here either and resolve that in the snap side of things.

Generally for recovery purposes you will be booting an image with an equal or newer version of Ubuntu.

Regarding Dimitri's comment about new kernel feature support in 5.15, that doesn't seem related to this issue, and I'm not sure we should be changing feature flag in a stable release anyhow.

Revision history for this message
Benjamin Drung (bdrung) wrote :

I ran into this bug myself a while ago by doing following: I bought a new NVMe and put it into my laptop. Then I booted a recent Ubuntu live system, created partitions on the NVMe, copied everything from the old to the new, updated entries in /etc/fstab etc. When I rebooted the file system check failed with that error message. I either re-did everything with a Ubuntu jammy live system or hot-replaced fsck in the initramfs by /bin/true and upgraded Ubuntu.

Revision history for this message
Theodore Ts'o (tytso) wrote :

For Debian the metadata_csum_seed and orphan_file features were disabled by default by changing the /etc/mke2fs.conf file.

e2fsprogs (1.47.0-2) unstable; urgency=medium

  * Don't enable metadata_csum_seed and orhpan_file by default (Closes:
    #1031622, #1030939)

 -- Theodore Y. Ts'o <email address hidden> Sat, 04 Mar 2023 22:16:08 -0500

Ubuntu Lunar and Mantic chose to only disable metadata_csum_seed:

e2fsprogs (1.47.0-1ubuntu1) lunar; urgency=low

  * Merge from Debian unstable. Remaining changes:
    - Use 4k blocksize in all ext4 mke2fs.conf stanzas, so lvm migration
      between non-4k PVs and 4k PVs works regardless of the volume size.
  * Disable the metadata_csum_seed feature again, as grub does not yet
    support it (Closes: #866603)

 -- Julian Andres Klode <email address hidden> Fri, 17 Feb 2023 11:58:55 +0100

It should be noted that users are always free to change /etc/mke2fs.conf, since that's a configuration file, and the whole point of that file is to make it easy for distributions and users to customize how they mke2fs should behave. So if you think that Ubuntu Mantic should be able create file systems that can be handled by Jammy, it's just a matter of adjusting the mke2fs.conf file in Mantic.

As far as grub support is concerned, the metadata_csum_seed feature flag is supposed by grub2 (2.06-8) or newer. And grub doesn't care about orphan_file, since it's a COMPAT flag. That is an issue for e2fsck, but not for grub. The question was always whether a distribution supports creating a file system that can be (a) mounted and/or (b) fsck'ed by an older distribution, and if so, for how many versions back. That's not something for which people of good will can disagree, which is why it can be made configurable.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package e2fsprogs - 1.47.0-1ubuntu2

---------------
e2fsprogs (1.47.0-1ubuntu2) mantic; urgency=medium

  * Temporarily disable orphan_file by default, such that fsck from jammy
    can check ext4 created in mantic. Given the new incompat ext4 features
    that v5.15 & hwe kernels support, ideally e2fsprogs 1.47.0 should be
    SRUed into jammy. LP: #2025339

 -- Dimitri John Ledkov <email address hidden> Thu, 29 Jun 2023 10:14:32 +0100

Changed in e2fsprogs (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.