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 <ty...@mit.edu> 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 <juli...@ubuntu.com> 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.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/2025339
Title:
FDE image fails to run e2fsck
Status in e2fsprogs package in Ubuntu:
Confirmed
Status in e2fsprogs source package in Jammy:
Confirmed
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2025339/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
