Your message dated Sun, 05 Mar 2023 04:04:08 +0000
with message-id <e1pyfbu-00hp4a...@fasolo.debian.org>
and subject line Bug#1031622: fixed in e2fsprogs 1.47.0-2
has caused the Debian Bug report #1031622,
regarding mke2fs: should not enable orphan_file by default until trixie
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: grave
Justification: renders package unusable (at least for inexperienced users)
X-Debbugs-Cc: e2fspr...@packages.debian.org

Boot method: virtual CD
Image version: 
https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso
 dated 2023-02-09
Installation date: 2023-02-19

Machine: qemu VM, virt-manager "Debian testing" profile
Partitions: default guided partitioning on a 20G disk

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [O]
Detect network card:    [O]
Configure network:      [O]
Detect media:           [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:    [O]
Detect hard drives:     [O]
Partition hard drives:  [O]
Install base system:    [O]
Install tasks:          [O]
Install boot loader:    [O]
Overall install:        [E]

Comments/Problems:

Steps to reproduce
==================

I used the graphical installer, and installed with mostly default settings
(in particular the default guided partitioning with all files in one
ext4 partition).

Non-default settings, just in case they matter (but I'm fairly sure they
don't):

* en_GB instead of en_US;
* an apt proxy (http://192.168.122.1:3142 to use apt-cacher-ng on my
  host system);
* tasksel: LXDE instead of the default GNOME, and add a ssh server

Expected result
===============

The installed system boots.

Actual result
=============

Graphical installation proceeded normally (in particular #1031620 is
fixed in this weekly build). However, on booting the installed system
for the first time, I got this error:

> /dev/vda1 has unsupported feature(s): FEATURE_C12
> e2fsck: Get a newer version of e2fsck!
> 
> /dev/vda1: ***** WARNING: Filesystem still has errors *****
> 
> fsck exited with status code 12
> The root filesystem on /dev/vda1 requires a manual fsck

followed by an (initramfs) prompt.

Workaround
==========

Reset the VM and boot with "fsck.mode=skip" added to the kernel
command-line in grub. After booting like that once, upgrade e2fsprogs from
version 1.46.6-1 (in bookworm) to version 1.47.0-1 (in sid). The initramfs
is rebuilt and the rebuilt version can successfully fsck the filesystem.

Speculation
===========

I think this could be caused by debian-installer having udebs from
e2fsprogs 1.47.0-1 in the installation environment, so that the version
used to create the root filesystem has newer feature flags than the
installed version of e2fsck can cope with (similar to #1030939 and
#1031325).

If that theory is correct, then I think that even if the e2fsprogs
maintainer considers it to be important for mke2fs to create new
filesystems with default feature flags that are unsupported by Debian 11,
as a minimum mke2fs should be avoiding new feature flags until an e2fsck
that supports those flags has migrated to testing.

    smcv

--- End Message ---
--- Begin Message ---
Source: e2fsprogs
Source-Version: 1.47.0-2
Done: Theodore Y. Ts'o <ty...@mit.edu>

We believe that the bug you reported is fixed in the latest version of
e2fsprogs, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1031...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Theodore Y. Ts'o <ty...@mit.edu> (supplier of updated e2fsprogs package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 04 Mar 2023 22:16:08 -0500
Source: e2fsprogs
Architecture: source
Version: 1.47.0-2
Distribution: unstable
Urgency: medium
Maintainer: Theodore Y. Ts'o <ty...@mit.edu>
Changed-By: Theodore Y. Ts'o <ty...@mit.edu>
Closes: 1030939 1031622
Changes:
 e2fsprogs (1.47.0-2) unstable; urgency=medium
 .
   * Don't enable metadata_csum_seed and orhpan_file by default (Closes:
     #1031622, #1030939)
Checksums-Sha1:
 b747c64b353cc3c30958730fcd12e975176f77dc 2846 e2fsprogs_1.47.0-2.dsc
 1b25310584a519872c855fcbccf532e218c6b7e1 87328 e2fsprogs_1.47.0-2.debian.tar.xz
Checksums-Sha256:
 35b4de254e021f721362b767994598e249fea02e38ac446197cd9c22be1130fd 2846 
e2fsprogs_1.47.0-2.dsc
 3a756e08d300666039e34577293d11d70c7a1da7850fad478580a81af6348277 87328 
e2fsprogs_1.47.0-2.debian.tar.xz
Files:
 84cc53b9d71256586a5946f82b86c4c0 2846 admin required e2fsprogs_1.47.0-2.dsc
 d593f205ae4dc10bf0c563acf4cb24e5 87328 admin required 
e2fsprogs_1.47.0-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEK2m5VNv+CHkogTfJ8vlZVpUNgaMFAmQEECYACgkQ8vlZVpUN
gaO0nQf/dUsPwHO3qL+L9Pe+mdEx4LWSbO4RWsnwsapD6u7QX/UakYt8SDbp+xxH
NbDIzJcKd8CbKpeGNjiZa0iXCkJqDFZ1Jjp964JsxRecgkomrFOD3MQcXHsM2Ky9
XFQBymcyISFe+DVaK6swcSpgzaDyfWiviqCdavhoY89T7XfNVxfxAuAFf6YFp43Z
3ebMk6HcRzBb+eRbp4oYRS6cT8vpU9Cde5nfrgRLkPCNswpHaSPTvKS45zXPjhf2
JaWvUnGBPHBE0JL6y1hapUJ+fNkqgQ4PKX1gqwegJ0zJI+He3sK05+Ji2lhqnxNA
WTiRWITRDUKB9aUCsRu/z39eQuegHw==
=q4Gn
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to