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.boeckelm...@inoex.de<mailto:thore.boeckelm...@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.rap...@linaro.org> Gesendet: Mittwoch, 20. November 2024 13:04 An: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org>; Böckelmann, Thore <thore.boeckelm...@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
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#64310): https://lists.yoctoproject.org/g/yocto/message/64310 Mute This Topic: https://lists.yoctoproject.org/mt/109682386/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
