From: Henning Schild <henning.schild@siemens.com>
To: isar-users@googlegroups.com
Cc: Christian Storm <christian.storm@siemens.com>,
Henning Schild <henning.schild@siemens.com>
Subject: [PATCH] expand-on-first-boot: run systemd service before local-fs-pre.target
Date: Tue, 21 Jan 2020 19:15:22 +0100 [thread overview]
Message-ID: <20200121181522.18134-1-henning.schild@siemens.com> (raw)
From: Henning Schild <henning.schild@siemens.com>
In case that last partition is one of the local filesystems and not the
rootfs we have to be done with the expansion before systemd tries to
mount that filesystem.
Depending on the execution order and speed it was likely to get dropped
into a rescue shell when the resize and the mount happened at the same
time. That problem should be gone with this patch.
Signed-off-by: Henning Schild <henning.schild@siemens.com>
---
.../{expand-on-first-boot.bb => expand-on-first-boot_1.1.bb} | 0
.../expand-on-first-boot/files/expand-on-first-boot.service | 2 +-
2 files changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/expand-on-first-boot/{expand-on-first-boot.bb => expand-on-first-boot_1.1.bb} (100%)
diff --git a/meta/recipes-support/expand-on-first-boot/expand-on-first-boot.bb b/meta/recipes-support/expand-on-first-boot/expand-on-first-boot_1.1.bb
similarity index 100%
rename from meta/recipes-support/expand-on-first-boot/expand-on-first-boot.bb
rename to meta/recipes-support/expand-on-first-boot/expand-on-first-boot_1.1.bb
diff --git a/meta/recipes-support/expand-on-first-boot/files/expand-on-first-boot.service b/meta/recipes-support/expand-on-first-boot/files/expand-on-first-boot.service
index cbe3857a..404b9c93 100644
--- a/meta/recipes-support/expand-on-first-boot/files/expand-on-first-boot.service
+++ b/meta/recipes-support/expand-on-first-boot/files/expand-on-first-boot.service
@@ -8,7 +8,7 @@ Description=Expand last partition
DefaultDependencies=no
Conflicts=shutdown.target
After=systemd-remount-fs.service
-Before=sysinit.target shutdown.target
+Before=local-fs-pre.target shutdown.target
ConditionPathIsReadWrite=/etc
[Service]
--
2.24.1
next reply other threads:[~2020-01-21 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 18:15 Henning Schild [this message]
2020-03-09 10:58 ` Baurzhan Ismagulov
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=20200121181522.18134-1-henning.schild@siemens.com \
--to=henning.schild@siemens.com \
--cc=christian.storm@siemens.com \
--cc=isar-users@googlegroups.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