Further to a conversation in #ubuntu-devel I'm setting the Lunar task to
Won't Fix. Further details:
https://irclogs.ubuntu.com/2023/11/15/%23ubuntu-devel.html
** Changed in: e2fsprogs (Ubuntu Lunar)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a
SRU abandoned to not change the expected default behavior in lunar.
--
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
** Description changed:
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
** Tags added: foundations-todo
--
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:
** Changed in: e2fsprogs (Debian)
Status: Unknown => Fix Released
--
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
Also, given that this is the second time this kind of thing has
happened, perhaps it is appropriate to add a dep8 test to ensure that
the compatibility "level" of the default has not regressed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
(in the development release)
--
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:
Fix
> So if we disable this by default, I think it should only impact
performances of generated filesystems and probably not break anything
else.
This sounds like it could be insignificant, or a major performance
regression in some use cases. It's not clear which. Presumably
orphan_file was
** No longer affects: e2fsprogs (Ubuntu Jammy)
--
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
** Description changed:
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
** Also affects: e2fsprogs (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031622
Importance: Unknown
Status: Unknown
** Changed in: e2fsprogs (Ubuntu Lunar)
Status: Confirmed => In Progress
** Changed in: e2fsprogs (Ubuntu Lunar)
Assignee: (unassigned)
** Merge proposal linked:
https://code.launchpad.net/~upils/ubuntu/+source/e2fsprogs/+git/e2fsprogs/+merge/454796
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
** Description changed:
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
** Also affects: e2fsprogs (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: e2fsprogs (Ubuntu Lunar)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in
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 &
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 Sat, 04
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
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: e2fsprogs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: e2fsprogs (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
Related debian bug: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1031622
** Bug watch added: Debian Bug tracker #1031622
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031622
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Given new incompatible RO and RW features in ext4 that v5.15 kernels
support, imho we should SRU backport of e2fsprogs on HWE grounds.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
** Description changed:
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
** Also affects: e2fsprogs (Ubuntu Jammy)
Importance: Undecided
Status: New
--
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
** Description changed:
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
- Jun 21 12:48:19 ubuntu systemd-fsck[268]: e2fsck: Get a newer version of
** Description changed:
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
+ Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported
26 matches
Mail list logo
