From: Jan-Simon Moeller <dl9pf@gmx.de>
To: "Böckelmann, Thore" <thore.boeckelmann@inoex.de>,
yocto@lists.yoctoproject.org, mikko.rapeli@linaro.org
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] ext4 issues with scarthgap .wic image
Date: Thu, 21 Nov 2024 15:02:51 +0100 [thread overview]
Message-ID: <3616744.dWV9SEqChM@monster> (raw)
In-Reply-To: <Zz78VhN_AkYV3Xys@nuoska>
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
prev parent reply other threads:[~2024-11-21 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ed7dbfe9-1861-4e5b-9954-03bf8404920a.970c85df-582b-4473-a7de-31be6a2b58c9.8a47a721-58ad-47e5-be44-609511a60ac9@emailsignatures365.codetwo.com>
[not found] ` <ed7dbfe9-1861-4e5b-9954-03bf8404920a.5f629621-7c71-47da-aee6-727c8a7b4e6a.21f4d927-51fb-4187-a3f2-1b08161ff7e2@emailsignatures365.codetwo.com>
2024-11-20 11:37 ` ext4 issues with scarthgap .wic image Böckelmann, Thore
2024-11-20 12:04 ` [yocto] " Mikko Rapeli
2024-11-20 12:42 ` AW: [EXT] " Böckelmann, Thore
2024-11-20 12:50 ` Mikko Rapeli
2024-11-21 9:18 ` AW: [EXT] " Böckelmann, Thore
2024-11-21 9:24 ` Mikko Rapeli
2024-11-21 14:02 ` Jan-Simon Moeller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3616744.dWV9SEqChM@monster \
--to=dl9pf@gmx.de \
--cc=mikko.rapeli@linaro.org \
--cc=thore.boeckelmann@inoex.de \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.