From: Raphael Lisicki <raphael.lisicki@siemens.com>
To: Henning Schild <henning.schild@siemens.com>,
"Bezdeka, Florian (T CED SES-DE)" <florian.bezdeka@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"MacDonald, Joe (DI SW CAS ES TO)" <joe.macdonald@siemens.com>,
"Schmidl, Tobias (T CED SES-DE)" <tobiasschmidl@siemens.com>
Subject: Re: [PATCH v6 0/1] expand-on-first-boot: Switch from resize2fs to systemd-growfs
Date: Fri, 28 Oct 2022 16:34:00 +0200 [thread overview]
Message-ID: <819739fc-38cd-18b8-4578-35b7cabb2813@siemens.com> (raw)
In-Reply-To: <20221025163131.6138db34@md1za8fc.ad001.siemens.net>
On 25.10.22 16:31, Henning Schild wrote:
>
> I have read that thread and pointed out there that systemd resize will
> be coming, and that people can try it already to see if it solves their
> problem. Will take Raphael in Cc.
>
> Raphael please have a look at the following patch, it might just solve
> your resize race.
>
I did not manage to test this yet, but I found quite some documentation
by systemd on the very same issue [1] and its shortcomings. I would be
moderately confident that systemd resize and systemd-udev will not clash.
The mentioned udevadm lock command is not available with debian bullseye.
[1] https://systemd.io/BLOCK_DEVICE_LOCKING/
best regards
raphael
prev parent reply other threads:[~2022-10-28 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 13:47 Henning Schild
2022-10-25 13:47 ` [PATCH v6 1/1] " Henning Schild
2022-10-25 15:34 ` Henning Schild
2022-10-25 13:49 ` [PATCH v6 0/1] " Henning Schild
2022-10-25 13:55 ` Bezdeka, Florian
2022-10-25 14:31 ` Henning Schild
2022-10-28 14:34 ` Raphael Lisicki [this message]
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=819739fc-38cd-18b8-4578-35b7cabb2813@siemens.com \
--to=raphael.lisicki@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=joe.macdonald@siemens.com \
--cc=tobiasschmidl@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