From: Adithya Balakumar <Adithya.Balakumar@toshiba-tsip.com>
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, kazuhiro3.hayashi@toshiba.co.jp,
dinesh.kumar@toshiba-tsip.com,
shivanand.kunijadar@toshiba-tsip.com,
sai.sathujoda@toshiba-tsip.com,
adithya.balakumar@toshiba-tsip.com
Subject: [PATCH v1 0/1] Use oe.utils.directory_size() instead of du for calculating rootfs size
Date: Fri, 29 Nov 2024 11:58:25 +0530 [thread overview]
Message-ID: <20241129062827.527177-1-Adithya.Balakumar@toshiba-tsip.com> (raw)
Currently the "du" command is used to calculate the rootfs size, and sometimes the
reported size of the rootfs by du varies across multiple builds (usually by a few kb).
But the rootfs contents are reproducible.
Although this does not affect any functionality, but it does affect reproducibility
of artifacts that rely on the calculated rootfs size.
There are 2 scenarios (that I noticed) where this is affects reproducibility:
1. In the case where no size parameter is set for a rootfs partition in the wks file,
wic uses the calculated rootfs size.
2. ext4 filesystem images with the IMAGE_CMD of isar, relies on rootfs size to create image.
Some of the files/directories in the rootfs has different number of blocks allocated.
The files/directories affected are not always the same across builds.
Using the "du" command to measure the size of the rootfs directory in such a case, yields
different values for the ROOTFS_SIZE.
This patch introduces the use of an alternate function from oe.utils to calculate the
directory size. OE-Core uses the same function to calculate the directory size (See [1])
Based on multiple build runs, usage of this function seems to give consistent size results.
Some details on the issue is mentioned in the below thread in the ISAR mailing list (See [2])
[1] https://github.com/openembedded/openembedded-core/commit/d8f1f3a6b024a2ae6631d1ce25421e8d94b69a12
[2] https://groups.google.com/g/isar-users/c/Ll7t4G41Lfo/m/gvxR4hYBAwAJ
Adithya Balakumar (1):
image.bbclass: use oe.utils.directory_size() instead of du
meta/classes/image.bbclass | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
--
2.39.5
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20241129062827.527177-1-Adithya.Balakumar%40toshiba-tsip.com.
next reply other threads:[~2024-11-29 6:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 6:28 Adithya Balakumar [this message]
2024-11-29 6:28 ` [PATCH v1 1/1] image.bbclass: use oe.utils.directory_size() instead of du Adithya Balakumar
2024-12-06 7:29 ` [PATCH v1 0/1] Use oe.utils.directory_size() instead of du for calculating rootfs size Uladzimir Bely
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=20241129062827.527177-1-Adithya.Balakumar@toshiba-tsip.com \
--to=adithya.balakumar@toshiba-tsip.com \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
--cc=sai.sathujoda@toshiba-tsip.com \
--cc=shivanand.kunijadar@toshiba-tsip.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox