ext4 issues with scarthgap .wic image

ext4 issues with scarthgap .wic image

[Böckelmann, Thore]

[-- Attachment #1: Type: text/plain, Size: 2678 bytes --]

Hi!

I am building an image for an iMX8 system and recently upgraded from hardknott to scarthgap. The image (wic.bz2) is created successfully, but after deploying it to an SD card I am not able to resize the partition via resize2fs. resize2fs always tells that the filesystem is using unsupported features.

After investigating further with gparted I found out that the ext4 partition was created with the C12 feature (orphan_file). I am using Ubuntu 22 and hence use resize2fs 1.46.5. There are some forum which suggest resize2fs 1.47.x as a workaround, but I don't cannot upgrade that easily to Ubuntu 23 or 24 yet.

I also built another image for an iMX93 system based on mickledore where I experience EXACTLY the same issue. For that system it was sufficient to add this line to conf/local.conf:
EXTRA_IMAGECMD:ext4 += " -O ^orphan_file"

After that the created ext4 filesystem was compatible to Ubuntu 22's resize2fs 1.46.5 again.

Unfortunately this did not help für the scarthgap build. No matter what I try, the additional options don't make their way to the call of mkfs.ext4.

What am I doing wrong and what can I do about that? What is the difference between mickledore and scarthgap in this respect?

Mit freundlichem Gruß
best regards

iNOEX GmbH
Thore Böckelmann
Software Design

Mit freundlichen Grüßen / Kind regards
i. A. Thore Böckelmann



iNOEX GmbH | Maschweg 70 | 49324 Melle | Germany | www.inoex.de<http://www.inoex.de/>

Dipl.-Inform. Thore Böckelmann
Software Engineering
thore.boeckelmann@inoex.de<mailto:thore.boeckelmann@inoex.de>

FON +49 5422 60507-958<callto:+49%205422%2060507-958> | FAX +49 5422 60507-101<callto:+49%205422%2060507-101>

A CiTEX Group Company



Follow us on  [cid:signatur_linkedin_612a1331-e3ca-46d8-92e7-c497d1f53ff6.png] <https://www.linkedin.com/company/3911295>   <https://plus.google.com/113636118318392148063> <https://plus.google.com/113636118318392148063>

[cid:inoex_logo_4c_fcc47c5f-1f79-48a0-b1e7-7629d7b99d29.png]


[cid:mail-signatur_spareparts_da655482-2557-4cdb-bcb2-384534f916c2.png]<mailto:%20spareparts@inoex.de>

[cid:mail-signatur_newsletter_de_5f1c5205-8ce1-49ad-bae5-fc3f06d35ab9.png]<https://www.inoex.de/#newsletter>

________________________________

iNOEX GmbH
Innovationen und Ausruestungen fuer die Extrusionstechnik

Geschaeftsfuehrer / Managing Director: Martin Deters, Jan Lohoff
Sitz der Gesellschaft / Headquarter: Maschweg 70, D-49324 Melle
Registergericht / Register: Amtsgericht Osnabrück
Handelsregisternummer / Registration number: HRB 207338

Bitte beachten Sie die Datenschutzinformationen <https://www.inoex.de/datenschutz/>

[-- Attachment #2.1: Type: text/html, Size: 8243 bytes --]

[-- Attachment #2.2: signatur_linkedin_612a1331-e3ca-46d8-92e7-c497d1f53ff6.png --]
[-- Type: image/png, Size: 767 bytes --]

[-- Attachment #2.3: inoex_logo_4c_fcc47c5f-1f79-48a0-b1e7-7629d7b99d29.png --]
[-- Type: image/png, Size: 28277 bytes --]

[-- Attachment #2.4: mail-signatur_spareparts_da655482-2557-4cdb-bcb2-384534f916c2.png --]
[-- Type: image/png, Size: 94074 bytes --]

[-- Attachment #2.5: mail-signatur_newsletter_de_5f1c5205-8ce1-49ad-bae5-fc3f06d35ab9.png --]
[-- Type: image/png, Size: 94298 bytes --]

Re: [yocto] ext4 issues with scarthgap .wic image

[Mikko Rapeli]

Hi,

On Wed, Nov 20, 2024 at 11:37:51AM +0000, tboeckel via lists.yoctoproject.org wrote:
> Hi!
> 
> I am building an image for an iMX8 system and recently upgraded from hardknott to scarthgap. The image (wic.bz2) is created successfully, but after deploying it to an SD card I am not able to resize the partition via resize2fs. resize2fs always tells that the filesystem is using unsupported features.
> 
> After investigating further with gparted I found out that the ext4 partition was created with the C12 feature (orphan_file). I am using Ubuntu 22 and hence use resize2fs 1.46.5. There are some forum which suggest resize2fs 1.47.x as a workaround, but I don't cannot upgrade that easily to Ubuntu 23 or 24 yet.
> 
> I also built another image for an iMX93 system based on mickledore where I experience EXACTLY the same issue. For that system it was sufficient to add this line to conf/local.conf:
> EXTRA_IMAGECMD:ext4 += " -O ^orphan_file"
> 
> After that the created ext4 filesystem was compatible to Ubuntu 22's resize2fs 1.46.5 again.
> 
> Unfortunately this did not help f�r the scarthgap build. No matter what I try, the additional options don't make their way to the call of mkfs.ext4.
> 
> What am I doing wrong and what can I do about that? What is the difference between mickledore and scarthgap in this respect?

I think these kind of changes are expected in yocto major version updates.
If new ext4 etc features would need to be explicitly enabled, then users
and maintainers would be flooded with them. Upstream defaults are better
even if they sometimes are not backwards compatible.

I would not expect yocto tooling to always be compatible with other Linux distros
so I would rather add the resize2fs etc partition resize tooling to the
image itself and resize partition(s) on the target at runtime. This can be
part of the target 'flashing' process. This is IMO more future proof.

Cheers,

-Mikko

AW: [EXT] Re: [yocto] ext4 issues with scarthgap .wic image

[Böckelmann, Thore]

[-- Attachment #1: Type: text/plain, Size: 3664 bytes --]

Hi Mikko!

Of course it is always better to move forward instead of backwards. But my point is that the documented EXTRA_IMAGECMD variable is somehow ignored and not passed to mkfs.ext4 as it should be. If it isn't to disable a feature the same issue will arise when I try to pass any other option to mkfs.ext4. This is what the IMAGE_CMD and EXTRA_IMAGECMD variables were invented for.

Mit freundlichem Gruß
best regards

iNOEX GmbH
Thore Böckelmann
Software Design

Mit freundlichen Grüßen / Kind regards
i. A. Thore Böckelmann



[cid:inoex_logo_4c_982191a2-b996-4578-8ee9-9a0ca87b6136.png]<https://inoex.de>


Dipl.-Inform. Thore Böckelmann
Software Engineering
thore.boeckelmann@inoex.de<mailto:thore.boeckelmann@inoex.de>

FON +49 5422 60507-958<callto:+49%205422%2060507-958> | FAX +49 5422 60507-101<callto:+49%205422%2060507-101>

A CiTEX Group Company






________________________________

iNOEX GmbH
Innovationen und Ausruestungen fuer die Extrusionstechnik

Geschaeftsfuehrer / Managing Director: Martin Deters, Jan Lohoff
Sitz der Gesellschaft / Headquarter: Maschweg 70, D-49324 Melle
Registergericht / Register: Amtsgericht Osnabrück
Handelsregisternummer / Registration number: HRB 207338

Bitte beachten Sie die Datenschutzinformationen <https://www.inoex.de/datenschutz/>

________________________________
Von: Mikko Rapeli <mikko.rapeli@linaro.org>
Gesendet: Mittwoch, 20. November 2024 13:04
An: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org>; Böckelmann, Thore <thore.boeckelmann@inoex.de>
Betreff: [EXT] Re: [yocto] ext4 issues with scarthgap .wic image

Diese Nachricht wurde von außerhalb unserer Organisation gesendet.



Hi,

On Wed, Nov 20, 2024 at 11:37:51AM +0000, tboeckel via lists.yoctoproject.org wrote:
> Hi!
>
> I am building an image for an iMX8 system and recently upgraded from hardknott to scarthgap. The image (wic.bz2) is created successfully, but after deploying it to an SD card I am not able to resize the partition via resize2fs. resize2fs always tells that the filesystem is using unsupported features.
>
> After investigating further with gparted I found out that the ext4 partition was created with the C12 feature (orphan_file). I am using Ubuntu 22 and hence use resize2fs 1.46.5. There are some forum which suggest resize2fs 1.47.x as a workaround, but I don't cannot upgrade that easily to Ubuntu 23 or 24 yet.
>
> I also built another image for an iMX93 system based on mickledore where I experience EXACTLY the same issue. For that system it was sufficient to add this line to conf/local.conf:
> EXTRA_IMAGECMD:ext4 += " -O ^orphan_file"
>
> After that the created ext4 filesystem was compatible to Ubuntu 22's resize2fs 1.46.5 again.
>
> Unfortunately this did not help für the scarthgap build. No matter what I try, the additional options don't make their way to the call of mkfs.ext4.
>
> What am I doing wrong and what can I do about that? What is the difference between mickledore and scarthgap in this respect?

I think these kind of changes are expected in yocto major version updates.
If new ext4 etc features would need to be explicitly enabled, then users
and maintainers would be flooded with them. Upstream defaults are better
even if they sometimes are not backwards compatible.

I would not expect yocto tooling to always be compatible with other Linux distros
so I would rather add the resize2fs etc partition resize tooling to the
image itself and resize partition(s) on the target at runtime. This can be
part of the target 'flashing' process. This is IMO more future proof.

Cheers,

-Mikko

[-- Attachment #2.1: Type: text/html, Size: 6967 bytes --]

[-- Attachment #2.2: inoex_logo_4c_982191a2-b996-4578-8ee9-9a0ca87b6136.png --]
[-- Type: image/png, Size: 28277 bytes --]

Re: AW: [EXT] Re: [yocto] ext4 issues with scarthgap .wic image

[Mikko Rapeli]

Hi,

On Wed, Nov 20, 2024 at 12:42:51PM +0000, B�ckelmann, Thore wrote:
> Hi Mikko!
> 
> Of course it is always better to move forward instead of backwards. But my point is that the documented EXTRA_IMAGECMD variable is somehow ignored and not passed to mkfs.ext4 as it should be. If it isn't to disable a feature the same issue will arise when I try to pass any other option to mkfs.ext4. This is what the IMAGE_CMD and EXTRA_IMAGECMD variables were invented for.

This could be a bug, or change in image_types.bbclass behaviour.
Would be nice if you could debug this a bit further, for example
"bitbake -e image" output.

At least IMAGE_CMD:ext4 in current poky master image_types.bbclass
still has

IMAGE_CMD:ext4 = "oe_mkext234fs ext4 ${EXTRA_IMAGECMD}"

which would imply that adding command line arguments with
EXTRA_IMAGECMD should work.

Cheers,

-Mikko

AW: [EXT] Re: AW: [EXT] Re: [yocto] ext4 issues with scarthgap .wic image

[Böckelmann, Thore]

[-- Attachment #1: Type: text/plain, Size: 2612 bytes --]

Hi Mikko!

I found a different approach to resize the ext4 filesystem. Instead of doing this while deploying the .wic image to the SD card, I simply created a small systemd service, which does all the dirty work within the embedded system upon the first boot of the system. This works perfectly and completely independent of my build system.

Nevertheless, thanks for your help!

Mit freundlichem Gruß
best regards

iNOEX GmbH
Thore Böckelmann
Software Design

Mit freundlichen Grüßen / Kind regards
i. A. Thore Böckelmann



[cid:inoex_logo_4c_982191a2-b996-4578-8ee9-9a0ca87b6136.png]<https://inoex.de>


Dipl.-Inform. Thore Böckelmann
Software Engineering
thore.boeckelmann@inoex.de<mailto:thore.boeckelmann@inoex.de>

FON +49 5422 60507-958<callto:+49%205422%2060507-958> | FAX +49 5422 60507-101<callto:+49%205422%2060507-101>

A CiTEX Group Company






________________________________

iNOEX GmbH
Innovationen und Ausruestungen fuer die Extrusionstechnik

Geschaeftsfuehrer / Managing Director: Martin Deters, Jan Lohoff
Sitz der Gesellschaft / Headquarter: Maschweg 70, D-49324 Melle
Registergericht / Register: Amtsgericht Osnabrück
Handelsregisternummer / Registration number: HRB 207338

Bitte beachten Sie die Datenschutzinformationen <https://www.inoex.de/datenschutz/>

________________________________
Von: Mikko Rapeli <mikko.rapeli@linaro.org>
Gesendet: Mittwoch, 20. November 2024 13:50
An: Böckelmann, Thore <thore.boeckelmann@inoex.de>
Cc: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org>
Betreff: [EXT] Re: AW: [EXT] Re: [yocto] ext4 issues with scarthgap .wic image

Diese Nachricht wurde von außerhalb unserer Organisation gesendet.



Hi,

On Wed, Nov 20, 2024 at 12:42:51PM +0000, Böckelmann, Thore wrote:
> Hi Mikko!
>
> Of course it is always better to move forward instead of backwards. But my point is that the documented EXTRA_IMAGECMD variable is somehow ignored and not passed to mkfs.ext4 as it should be. If it isn't to disable a feature the same issue will arise when I try to pass any other option to mkfs.ext4. This is what the IMAGE_CMD and EXTRA_IMAGECMD variables were invented for.

This could be a bug, or change in image_types.bbclass behaviour.
Would be nice if you could debug this a bit further, for example
"bitbake -e image" output.

At least IMAGE_CMD:ext4 in current poky master image_types.bbclass
still has

IMAGE_CMD:ext4 = "oe_mkext234fs ext4 ${EXTRA_IMAGECMD}"

which would imply that adding command line arguments with
EXTRA_IMAGECMD should work.

Cheers,

-Mikko

[-- Attachment #2.1: Type: text/html, Size: 6021 bytes --]

[-- Attachment #2.2: inoex_logo_4c_982191a2-b996-4578-8ee9-9a0ca87b6136.png --]
[-- Type: image/png, Size: 28277 bytes --]

Re: AW: [EXT] Re: AW: [EXT] Re: [yocto] ext4 issues with scarthgap .wic image

[Mikko Rapeli]

Hi,

On Thu, Nov 21, 2024 at 09:18:13AM +0000, B�ckelmann, Thore wrote:
> Hi Mikko!
> 
> I found a different approach to resize the ext4 filesystem. Instead of doing this while deploying the .wic image to the SD card, I simply created a small systemd service, which does all the dirty work within the embedded system upon the first boot of the system. This works perfectly and completely independent of my build system.

Sounds good. Also systemd repartd is really handy for cases like this:

https://www.freedesktop.org/software/systemd/man/latest/systemd-repart.html
https://www.freedesktop.org/software/systemd/man/latest/repart.d.html

Cheers,

-Mikko

Re: [yocto] ext4 issues with scarthgap .wic image

[Jan-Simon Moeller]

Hi !

it is metadata_csum_seed and orphan_file . 

The change was introduced by an e2fsprogs update which deployed new defaults
and these are also used when creating the rootfs with a e2fsprogs-native .

Should be part of 1.47.1 and thus introduced here:
https://git.yoctoproject.org/poky/commit/meta/recipes-devtools/e2fsprogs?
id=453249e291817947af3d9cfdf8d1095ad1411f11

Upstream commit:
https://github.com/tytso/e2fsprogs/commit/
fe341d59ee9696f66ec8cd1bf9615ee1a107824f

We might dial-down the default a bit. But as Mikko said, we cannot stop 
evolution. But we can limit it where needed.

Best,
Jan-Simon


Am Donnerstag, 21. November 2024, 10:24:38 CET schrieb Mikko Rapeli via 
lists.yoctoproject.org:
> Hi,
> 
> On Thu, Nov 21, 2024 at 09:18:13AM +0000, Böckelmann, Thore wrote:
> > Hi Mikko!
> > 
> > I found a different approach to resize the ext4 filesystem. Instead of
> > doing this while deploying the .wic image to the SD card, I simply
> > created a small systemd service, which does all the dirty work within the
> > embedded system upon the first boot of the system. This works perfectly
> > and completely independent of my build system.
> Sounds good. Also systemd repartd is really handy for cases like this:
> 
> https://www.freedesktop.org/software/systemd/man/latest/systemd-repart.html
> https://www.freedesktop.org/software/systemd/man/latest/repart.d.html
> 
> Cheers,
> 
> -Mikko