| 2023-06-29 08:41:35 |
Jean-Baptiste Lallement |
bug |
|
|
added bug |
| 2023-06-29 08:41:58 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Jammy |
|
| 2023-06-29 08:41:58 |
Dimitri John Ledkov |
bug task added |
|
e2fsprogs (Ubuntu Jammy) |
|
| 2023-06-29 08:42:10 |
Alfonso Sanchez-Beato |
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 |
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 e2fsck!
Jun 21 12:48:19 ubuntu systemd-fsck[268]: ubuntu-boot: ********** WARNING: Filesystem still has errors **********
Jun 21 12:48:19 ubuntu systemd-fsck[265]: fsck failed with exit status 12.
Jun 21 12:48:19 ubuntu systemd-fsck[265]: Running request emergency.target/start/replace
Jun 21 12:48:19 ubuntu systemd[1]: systemd-fsck@dev-vda2.service: Main process exited, code=exited, status=1/FAILURE
Jun 21 12:48:19 ubuntu systemd[1]: systemd-fsck@dev-vda2.service: Failed with result 'exit-code'.
Jun 21 12:48:19 ubuntu systemd[1]: Failed to start File System Check on /dev/vda2.
Jun 21 12:48:19 ubuntu systemd[1]: Dependency failed for /run/mnt/ubuntu-boot.
Jun 21 12:48:19 ubuntu systemd[1]: run-mnt-ubuntu\x2dboot.mount: Job run-mnt-ubuntu\x |
|
| 2023-06-29 08:42:39 |
Dimitri John Ledkov |
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
Jun 21 12:48:19 ubuntu systemd-fsck[268]: e2fsck: Get a newer version of e2fsck!
Jun 21 12:48:19 ubuntu systemd-fsck[268]: ubuntu-boot: ********** WARNING: Filesystem still has errors **********
Jun 21 12:48:19 ubuntu systemd-fsck[265]: fsck failed with exit status 12.
Jun 21 12:48:19 ubuntu systemd-fsck[265]: Running request emergency.target/start/replace
Jun 21 12:48:19 ubuntu systemd[1]: systemd-fsck@dev-vda2.service: Main process exited, code=exited, status=1/FAILURE
Jun 21 12:48:19 ubuntu systemd[1]: systemd-fsck@dev-vda2.service: Failed with result 'exit-code'.
Jun 21 12:48:19 ubuntu systemd[1]: Failed to start File System Check on /dev/vda2.
Jun 21 12:48:19 ubuntu systemd[1]: Dependency failed for /run/mnt/ubuntu-boot.
Jun 21 12:48:19 ubuntu systemd[1]: run-mnt-ubuntu\x2dboot.mount: Job run-mnt-ubuntu\x |
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 |
|
| 2023-06-29 08:52:44 |
Dimitri John Ledkov |
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 |
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. |
|
| 2023-06-29 09:41:33 |
Alfonso Sanchez-Beato |
bug |
|
|
added subscriber Alfonso Sanchez-Beato |
| 2023-06-29 09:58:14 |
Alfonso Sanchez-Beato |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031622 |
|
| 2023-06-29 09:58:38 |
Launchpad Janitor |
e2fsprogs (Ubuntu): status |
New |
Confirmed |
|
| 2023-06-29 09:58:38 |
Launchpad Janitor |
e2fsprogs (Ubuntu Jammy): status |
New |
Confirmed |
|
| 2023-06-29 18:15:21 |
Benjamin Drung |
bug |
|
|
added subscriber Benjamin Drung |
| 2023-07-03 01:30:05 |
Launchpad Janitor |
e2fsprogs (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2023-10-30 07:41:25 |
Paul Mars |
nominated for series |
|
Ubuntu Lunar |
|
| 2023-10-30 07:41:25 |
Paul Mars |
bug task added |
|
e2fsprogs (Ubuntu Lunar) |
|
| 2023-10-30 07:41:31 |
Paul Mars |
e2fsprogs (Ubuntu Lunar): status |
New |
Confirmed |
|
| 2023-10-30 07:59:44 |
Paul Mars |
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. |
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.
[Impact]
See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot).
[ Test Plan ]
On lunar, generate a filesystem and check the orphan_file feature is enabled:
> dd if=/dev/zero of=test.img bs=100M count=1
> mkfs.ext4 test.img
> # Then check the orphan_file feature is enabled
> dumpe2fs test.img | grep orphan
Move this .img file to a jammy based machine, and try using resize2fs on it:
> resize2fs -d -f -M test.img
resize2fs 1.46.5 (30-Dec-2021)
resize2fs: Filesystem has unsupported feature(s) (test.img)
[Where problems could occur]
Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed.
The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. |
|
| 2023-10-30 08:01:20 |
Paul Mars |
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.
[Impact]
See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot).
[ Test Plan ]
On lunar, generate a filesystem and check the orphan_file feature is enabled:
> dd if=/dev/zero of=test.img bs=100M count=1
> mkfs.ext4 test.img
> # Then check the orphan_file feature is enabled
> dumpe2fs test.img | grep orphan
Move this .img file to a jammy based machine, and try using resize2fs on it:
> resize2fs -d -f -M test.img
resize2fs 1.46.5 (30-Dec-2021)
resize2fs: Filesystem has unsupported feature(s) (test.img)
[Where problems could occur]
Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed.
The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. |
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.
[Impact]
See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot).
[ Test Plan ]
On lunar, generate a filesystem and check the orphan_file feature is enabled:
$ dd if=/dev/zero of=test.img bs=100M count=1
$ mkfs.ext4 test.img
$ # Then check the orphan_file feature is enabled
$ dumpe2fs test.img | grep orphan
Move this .img file to a jammy based machine, and try using resize2fs on it:
$ resize2fs -d -f -M test.img
resize2fs 1.46.5 (30-Dec-2021)
resize2fs: Filesystem has unsupported feature(s) (test.img)
[Where problems could occur]
Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed.
The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. |
|
| 2023-10-31 17:37:16 |
Bryce Harrington |
merge proposal linked |
|
https://code.launchpad.net/~upils/ubuntu/+source/e2fsprogs/+git/e2fsprogs/+merge/454796 |
|
| 2023-10-31 17:52:12 |
Bryce Harrington |
bug task added |
|
e2fsprogs (Debian) |
|
| 2023-10-31 17:52:27 |
Bryce Harrington |
e2fsprogs (Ubuntu Lunar): status |
Confirmed |
In Progress |
|
| 2023-10-31 17:52:51 |
Bryce Harrington |
e2fsprogs (Ubuntu Lunar): assignee |
|
Paul Mars (upils) |
|
| 2023-11-02 08:20:56 |
Paul Mars |
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.
[Impact]
See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot).
[ Test Plan ]
On lunar, generate a filesystem and check the orphan_file feature is enabled:
$ dd if=/dev/zero of=test.img bs=100M count=1
$ mkfs.ext4 test.img
$ # Then check the orphan_file feature is enabled
$ dumpe2fs test.img | grep orphan
Move this .img file to a jammy based machine, and try using resize2fs on it:
$ resize2fs -d -f -M test.img
resize2fs 1.46.5 (30-Dec-2021)
resize2fs: Filesystem has unsupported feature(s) (test.img)
[Where problems could occur]
Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed.
The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. |
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.
[Fix]
This SRU is disabling 2 features (orphan_file and metadata_csum_seed) from ext4 to generate filesystems compatible with older series. Fixes come from debian (fixing #1031622, #1030939). This is only disabling the feature by default. One can still generate a filesystem with this feature by explicitly listing them when invoking mkfs.ext4.
[Impact]
See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot).
[ Test Plan ]
On lunar, generate a filesystem and check the orphan_file feature is enabled:
$ dd if=/dev/zero of=test.img bs=100M count=1
$ mkfs.ext4 test.img
$ # Then check the orphan_file feature is enabled
$ dumpe2fs test.img | grep orphan
Move this .img file to a jammy based machine, and try using resize2fs on it:
$ resize2fs -d -f -M test.img
resize2fs 1.46.5 (30-Dec-2021)
resize2fs: Filesystem has unsupported feature(s) (test.img)
[Where problems could occur]
Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed.
The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. |
|
| 2023-11-03 16:20:40 |
Paul Mars |
bug task deleted |
e2fsprogs (Ubuntu Jammy) |
|
|
| 2023-11-03 19:40:37 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2023-11-04 15:03:29 |
Bug Watch Updater |
e2fsprogs (Debian): status |
Unknown |
Fix Released |
|
| 2023-11-06 12:25:34 |
Paul Mars |
tags |
|
foundations-todo |
|
| 2023-11-15 09:19:24 |
Paul Mars |
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.
[Fix]
This SRU is disabling 2 features (orphan_file and metadata_csum_seed) from ext4 to generate filesystems compatible with older series. Fixes come from debian (fixing #1031622, #1030939). This is only disabling the feature by default. One can still generate a filesystem with this feature by explicitly listing them when invoking mkfs.ext4.
[Impact]
See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot).
[ Test Plan ]
On lunar, generate a filesystem and check the orphan_file feature is enabled:
$ dd if=/dev/zero of=test.img bs=100M count=1
$ mkfs.ext4 test.img
$ # Then check the orphan_file feature is enabled
$ dumpe2fs test.img | grep orphan
Move this .img file to a jammy based machine, and try using resize2fs on it:
$ resize2fs -d -f -M test.img
resize2fs 1.46.5 (30-Dec-2021)
resize2fs: Filesystem has unsupported feature(s) (test.img)
[Where problems could occur]
Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed.
The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. |
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.
[Fix]
This SRU is disabling 2 features (orphan_file and metadata_csum_seed) from ext4 to generate filesystems compatible with older series. Fixes come from debian (fixing #1031622, #1030939). This is only disabling the feature by default. One can still generate a filesystem with this feature by explicitly listing them when invoking mkfs.ext4. The decision to disable this feature by default has already been taken for mantic and is not planned to be revised soon as far as I know. So this fix is also useful to implement a common behavior between the 2 series (and following ones).
This fix is also motivated by the fact that snapd is using mkfs.ext4 without any options. The possibility to give options for mkfs.ext4 was removed in snapd at some point for good reasons and it would be more complex to handle a special case only for lunar in snapd than disabling this feature by default in e2fsprogs I think.
[Impact]
See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot).
[ Test Plan ]
On lunar, generate a filesystem and check the orphan_file feature is enabled:
$ dd if=/dev/zero of=test.img bs=100M count=1
$ mkfs.ext4 test.img
$ # Then check the orphan_file feature is enabled
$ dumpe2fs test.img | grep orphan
Move this .img file to a jammy based machine, and try using resize2fs on it:
$ resize2fs -d -f -M test.img
resize2fs 1.46.5 (30-Dec-2021)
resize2fs: Filesystem has unsupported feature(s) (test.img)
[Where problems could occur]
Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed.
The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else.
It should be noted that before lunar, users did not have access to this feature and since mantic it is disabled by default, so I suspect the population expecting this feature to be enabled by default is rather small. |
|
| 2023-11-15 16:02:45 |
Robie Basak |
e2fsprogs (Ubuntu Lunar): status |
In Progress |
Won't Fix |
|
