A new feature orphan_file was introduced:
The old <sys-fs/e2fsprogs-1.47.0 tools recognize it as FEATURE_C12
Systemd will stop booting and halt in emergency mode. One will find similar lines in the log:
Mar 27 04:02:05 hp systemd-fsck: /dev/sda3 has unsupported feature(s): FEATURE_C12
Mar 27 04:02:05 hp systemd-fsck: e2fsck: Get a newer version of e2fsck!
Mar 27 04:02:05 hp systemd-fsck: /dev/sda3: ********** WARNING: Filesystem still has errors **********
Mar 27 04:04:02 hp systemd: systemd-fsck-root.service was skipped because of an unmet condition check (ConditionPathIsReadWrite=!/).
tune2fs -l /dev/sda3
tune2fs 1.46.5 (30-Dec-2021)
Filesystem features: has_journal ext_attr resize_inode dir_index FEATURE_C12 filetype extent flex_bg metadata_csum_seed sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
after upgrading to sys-fs/e2fsprogs-1.47.0 the feature is known and the system will be able to run fsck again:
tune2fs -l /dev/sda3
tune2fs 1.47.0 (5-Feb-2023)
Filesystem features: has_journal ext_attr resize_inode dir_index orphan_file filetype needs_recovery extent flex_bg metadata_csum_seed sparse_super large_file huge_file dir_nlink extra_isize metadata_csum orphan_present
I write this ticket to help our users, because newer kernels were stabilized while the required sys-fs/e2fsprogs-1.47.0 was still unstable. Our current LiveUSB system is affected too.
I do not know, if other packages besides sys-fs/e2fsprogs need an update too.
We can close it, when sys-fs/e2fsprogs-1.47.0 is stable and LiveUSB is updated.
I think you probably created that disk with a newer version of e2fsprogs, it's not because of the kernel version.
The bug has been referenced in the following commit(s):
Author: Sam James <email@example.com>
AuthorDate: 2023-04-10 07:28:30 +0000
Commit: Sam James <firstname.lastname@example.org>
CommitDate: 2023-04-10 07:31:40 +0000
sys-fs/e2fsprogs: disable metadata_csum_seed and orphan_file features for new fs by default
This keeps support for metadata_csum_seed and orphan_file but doesn't *enable*
it by default in new filesystems.
Unfortunately, support was added in the same e2fsprogs release which enabled
it by default. By changing the defaults as Debian has, we give people a chance
to upgrade their initramfses, live media, etc, so they can actually mount partitions
created by such a new e2fsprogs.
It feels wrong to have to do this but I don't see much other choice. At least we're
in good company.
Signed-off-by: Sam James <email@example.com>
sys-fs/e2fsprogs/e2fsprogs-1.47.0-r1.ebuild | 172 +++++++++++++++++++++
...data_csum_seed-and-orphan_file-by-default.patch | 30 ++++
2 files changed, 202 insertions(+)