[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#1031622: d-i regression in weekly builds: FEATURE_C12 unsupported by the installed e2fsck

Control: reassign -1 src:e2fsprogs 1.47.0-1
Control: retitle -1 mke2fs: should not enable orphan_file by default until trixie
Control: affects -1 installation-reports

On Fri, 24 Feb 2023 at 18:43:05 +0100, Cyril Brulebois wrote:
> Simon McVittie <smcv@debian.org> (2023-02-24):
> > caused by the mke2fs in e2fsprogs/unstable ...
> Just to be clear: mke2fs from e2fsprogs-udeb/unstable

Yes, sorry, I meant src:e2fsprogs but the relevant binary package is
indeed e2fsprogs-udeb.

> > In that case this report should probably be reassigned to e2fsprogs,
> > as a request to stop enabling orphan_file by default until at least the
> > time that e2fsprogs (>= 1.47.0) has reached testing (but perhaps lower
> > risk to delay enabling it by default until post-bookworm).

Doing so now.

> The immediate issue should go away for Bookworm anyway:
>   https://bugs.debian.org/1031325#202

That's potentially somewhat orthogonal. If I understand it correctly,
#1031325 is mainly about the incompat feature "metadata_csum_seed" which
is unsupported by bullseye's grub, and because it's flagged as an incompat
feature, bullseye's grub assumes that it's invalid to do anything with
a filesystem with an incompat feature that it doesn't understand.

Meanwhile #1031622 is about a compat feature "orphan_file", which doesn't
need to be supported by the installed grub or kernel (because unknown
compat features are safe to ignore), but does need to be supported by the
installed e2fsck (because as a tool with in-depth ext[234] knowledge,
e2fsck is justifiably stricter about what filesystems it is willing to
work with).

I think the minimal-risk solution here is for bookworm's src:e2fsprogs to
revert the addition of both metadata_csum_seed and orphan_file to the
mke2fs defaults, so that filesystems are not created with those features
by default until trixie.


Reply to: