public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Tobias Schaffner <tobias.schaffner@siemens.com>,
	Henning Schild <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>,
	Christian Storm <christian.storm@siemens.com>
Subject: Re: [PATCH] expand-on-first-boot: Add support for devicemapper
Date: Fri, 22 Apr 2022 11:08:02 +0200	[thread overview]
Message-ID: <b67c96b7-d07c-cc90-d5b6-41bd07ccb447@siemens.com> (raw)
In-Reply-To: <32399d99-19e3-57b2-07c8-3f172302433b@siemens.com>

On 22.04.22 08:28, Tobias Schaffner wrote:
> Switching to systemd-repart would also fix a rare race condition.
> Expand-on-first-boot can cause systemd to not be able to mount its mount
> units if it makes the kernel reload the partition table in a bad moment.
> 

That is to be proven, but it would be valuable to check. I just "lost"
my reproduction case on the IOT2050 by dropping the pattern that
triggered it. If you still have it, please check that!

Jan

PS: Avoid top-posing on mailing lists ;)

-- 
Siemens AG, Technology
Competence Center Embedded Linux

  parent reply	other threads:[~2022-04-22  9:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21 17:10 Jan Kiszka
2022-04-21 17:43 ` Henning Schild
2022-04-21 18:49   ` Jan Kiszka
2022-04-21 19:05   ` Henning Schild
2022-04-22  6:28     ` Tobias Schaffner
2022-04-22  7:21       ` Henning Schild
2022-04-22  9:08       ` Jan Kiszka [this message]
2022-05-14 14:05 ` Anton Mikanovich
2022-05-19 11:51   ` Moessbauer, Felix
2022-05-19 12:23     ` Henning Schild

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=b67c96b7-d07c-cc90-d5b6-41bd07ccb447@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=christian.storm@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=tobias.schaffner@siemens.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