public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
* [PATCH 0/1] Don't run update-initramfs with enable-fsck
@ 2022-01-21  7:42 Uladzimir Bely
  2022-01-21  7:42 ` [PATCH 1/1] enable-fsck: don't run update-initramfs after fstab modification Uladzimir Bely
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Uladzimir Bely @ 2022-01-21  7:42 UTC (permalink / raw)
  To: isar-users

The enable-fsck recipe installs into the system the script that sets
'fs_passno' fields for the partitions in fstab. After that, it calls
'update-initramfs -u' that takes several minutes to run.

In CI this sometimes causes fails with 'run_vm' tests while there is
no proper command prompt after expected timeout, especially if CI
server is highly loaded.

Actually, there were several targets checked. All of them had empty
fstab in their generated initramfs images. So, 'update-initramfs -u'
just takes much time but doesn't really change anything and may be
omitted.

Anyway, something could be overlooked during investigations, so if we
really need initramfs update at first run, it would be nice to know
exactly why.

Uladzimir Bely (1):
  enable-fsck: don't run update-initramfs after fstab modification

 meta/recipes-support/enable-fsck/files/enable-fsck.sh | 2 --
 1 file changed, 2 deletions(-)

-- 
2.20.1


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [PATCH 1/1] enable-fsck: don't run update-initramfs after fstab modification
  2022-01-21  7:42 [PATCH 0/1] Don't run update-initramfs with enable-fsck Uladzimir Bely
@ 2022-01-21  7:42 ` Uladzimir Bely
  2022-01-25  6:46 ` [PATCH 0/1] Don't run update-initramfs with enable-fsck Jan Kiszka
  2022-02-14 10:18 ` Anton Mikanovich
  2 siblings, 0 replies; 4+ messages in thread
From: Uladzimir Bely @ 2022-01-21  7:42 UTC (permalink / raw)
  To: isar-users

On first machine run, if enable-fsck recipe was enabled, it takes
much time to start because of spending too much time on
the 'update-initramfs -u' call.

Removing it while it really does nothing useful.

Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
 meta/recipes-support/enable-fsck/files/enable-fsck.sh | 2 --
 1 file changed, 2 deletions(-)

diff --git a/meta/recipes-support/enable-fsck/files/enable-fsck.sh b/meta/recipes-support/enable-fsck/files/enable-fsck.sh
index d09e35df..72d6bd78 100644
--- a/meta/recipes-support/enable-fsck/files/enable-fsck.sh
+++ b/meta/recipes-support/enable-fsck/files/enable-fsck.sh
@@ -12,5 +12,3 @@ set -e
 ROOT_DEV="$(/bin/findmnt -n -o SOURCE /)"
 sed -i -e 's|^/dev/root\([ 	]\+.*[ 	]\+\)0[ 	]\+0|'"$ROOT_DEV"'\10	1|' \
        -e 's|^\(/dev/.*[ 	]\+\)0[ 	]\+0|\10	2|' /etc/fstab
-
-update-initramfs -u
-- 
2.20.1


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH 0/1] Don't run update-initramfs with enable-fsck
  2022-01-21  7:42 [PATCH 0/1] Don't run update-initramfs with enable-fsck Uladzimir Bely
  2022-01-21  7:42 ` [PATCH 1/1] enable-fsck: don't run update-initramfs after fstab modification Uladzimir Bely
@ 2022-01-25  6:46 ` Jan Kiszka
  2022-02-14 10:18 ` Anton Mikanovich
  2 siblings, 0 replies; 4+ messages in thread
From: Jan Kiszka @ 2022-01-25  6:46 UTC (permalink / raw)
  To: Uladzimir Bely, isar-users

On 21.01.22 08:42, Uladzimir Bely wrote:
> The enable-fsck recipe installs into the system the script that sets
> 'fs_passno' fields for the partitions in fstab. After that, it calls
> 'update-initramfs -u' that takes several minutes to run.
> 
> In CI this sometimes causes fails with 'run_vm' tests while there is
> no proper command prompt after expected timeout, especially if CI
> server is highly loaded.
> 
> Actually, there were several targets checked. All of them had empty
> fstab in their generated initramfs images. So, 'update-initramfs -u'
> just takes much time but doesn't really change anything and may be
> omitted.
> 
> Anyway, something could be overlooked during investigations, so if we
> really need initramfs update at first run, it would be nice to know
> exactly why.
> 

I don't recall details about this anymore. I would just recommend to 
check if there are any differences in buster vs. newer versions. Stretch 
is no longer supported, but I think it was the target back then, and 
maybe that did something different /wrt the initramfs.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH 0/1] Don't run update-initramfs with enable-fsck
  2022-01-21  7:42 [PATCH 0/1] Don't run update-initramfs with enable-fsck Uladzimir Bely
  2022-01-21  7:42 ` [PATCH 1/1] enable-fsck: don't run update-initramfs after fstab modification Uladzimir Bely
  2022-01-25  6:46 ` [PATCH 0/1] Don't run update-initramfs with enable-fsck Jan Kiszka
@ 2022-02-14 10:18 ` Anton Mikanovich
  2 siblings, 0 replies; 4+ messages in thread
From: Anton Mikanovich @ 2022-02-14 10:18 UTC (permalink / raw)
  To: Uladzimir Bely, isar-users

21.01.2022 10:42, Uladzimir Bely wrote:
> The enable-fsck recipe installs into the system the script that sets
> 'fs_passno' fields for the partitions in fstab. After that, it calls
> 'update-initramfs -u' that takes several minutes to run.
>
> In CI this sometimes causes fails with 'run_vm' tests while there is
> no proper command prompt after expected timeout, especially if CI
> server is highly loaded.
>
> Actually, there were several targets checked. All of them had empty
> fstab in their generated initramfs images. So, 'update-initramfs -u'
> just takes much time but doesn't really change anything and may be
> omitted.
>
> Anyway, something could be overlooked during investigations, so if we
> really need initramfs update at first run, it would be nice to know
> exactly why.
>
> Uladzimir Bely (1):
>    enable-fsck: don't run update-initramfs after fstab modification
>
>   meta/recipes-support/enable-fsck/files/enable-fsck.sh | 2 --
>   1 file changed, 2 deletions(-)
>
Applied to next, thanks.


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2022-02-14 10:18 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-21  7:42 [PATCH 0/1] Don't run update-initramfs with enable-fsck Uladzimir Bely
2022-01-21  7:42 ` [PATCH 1/1] enable-fsck: don't run update-initramfs after fstab modification Uladzimir Bely
2022-01-25  6:46 ` [PATCH 0/1] Don't run update-initramfs with enable-fsck Jan Kiszka
2022-02-14 10:18 ` Anton Mikanovich

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox