public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Schaffner, Tobias" <tobias.schaffner@siemens.com>
To: "MOESSBAUER, FELIX JONATHAN" <felix.moessbauer@siemens.com>,
	"roberto.foglietta@gmail.com" <roberto.foglietta@gmail.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH] In expand last partition wait for udev have finished
Date: Tue, 13 Dec 2022 08:44:02 +0000	[thread overview]
Message-ID: <17231259-4c30-c3bb-389b-bb10bd342c1f@siemens.com> (raw)
In-Reply-To: <86e6eb976cf7bd6396b2d54b807bfab54310bdbf.camel@siemens.com>

On 13.12.22 03:01, Moessbauer, Felix wrote:
> On Mon, 2022-12-12 at 20:23 +0000, roberto.foglietta@gmail.com wrote:
>> From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
>>
>> bugfix, expand last partition, wait for udev completion
>>
>> On some hardware the udev did not created the links to the disk
>> partitions
>> while this script is working thus it fails. This patch fixes that
>> cases.
>>
>> Signed-off-by: Roberto A. Foglietta <roberto.foglietta@gmail.com>
>> ---
>>   .../expand-on-first-boot/files/expand-last-partition.sh         | 2
>> ++
>>   1 file changed, 2 insertions(+)
>>
>> diff --git a/meta/recipes-support/expand-on-first-boot/files/expand-
>> last-partition.sh b/meta/recipes-support/expand-on-first-
>> boot/files/expand-last-partition.sh
>> index acfef8a..68e6698 100755
>> --- a/meta/recipes-support/expand-on-first-boot/files/expand-last-
>> partition.sh
>> +++ b/meta/recipes-support/expand-on-first-boot/files/expand-last-
>> partition.sh
>> @@ -9,6 +9,8 @@
>>   
>>   set -e
>>   
>> +udevadm settle
> 
> Hi Roberto,
> 
> thanks for this patch.
> I thought about something like that as well.
> If that reliably works, I vote to simply add this line instead of -
> again - re-writing this component.
> 
> Felix

Hi Felix, hi Roberto,

udev is started via systemd-udevd and this service might not be up
yet when the script runs.

Adding this line would only work reliably if we add
Requires=systemd-udevd and After=systemd-udevd to the
expand-on-first-boot.service

But adding this dependency might obviously increase the boot time.

Best,
Tobias

>> +
>>   ROOT_DEV="$(findmnt / -o source -n)"
>>   ROOT_DEV_NAME=${ROOT_DEV##*/}
>>   ROOT_DEV_SLAVE=$(find /sys/block/"${ROOT_DEV_NAME}"/slaves -mindepth
>> 1 -print -quit 2>/dev/null || true)
>> -- 
>> 2.34.1
>>
>>
>> https://16F0H.trk.elasticemail.com/tracking/unsubscribe?d=uQeFOzkk8plXVVZ2VnEcpnRSdsZJXyyuanyoKUe_hgUtRGm67z-BYxoD4dUduarMjrGtkXTgZjMZXUuF072gCX_KXuQap6OFDQDgYq9jqpv90
>>
> 

  reply	other threads:[~2022-12-13  8:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 20:23 roberto.foglietta
2022-12-13  2:01 ` Moessbauer, Felix
2022-12-13  8:44   ` Schaffner, Tobias [this message]
2022-12-13 10:03     ` Roberto A. Foglietta
2022-12-12 20:33 Roberto A. Foglietta

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=17231259-4c30-c3bb-389b-bb10bd342c1f@siemens.com \
    --to=tobias.schaffner@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=roberto.foglietta@gmail.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