public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
Cc: "jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
	"christian.storm@siemens.com" <christian.storm@siemens.com>,
	isar-users <isar-users@googlegroups.com>,
	Anton Mikanovich <amikan@ilbers.de>,
	"Schmidl, Tobias" <tobiasschmidl@siemens.com>
Subject: Re: [PATCH] expand-on-first-boot: Add support for devicemapper
Date: Thu, 19 May 2022 14:23:04 +0200	[thread overview]
Message-ID: <20220519142304.3326743e@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <AM9PR10MB4869F2EA1D4568EC3094EEF589D09@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM>

Am Thu, 19 May 2022 11:51:01 +0000
schrieb "Moessbauer, Felix" <felix.moessbauer@siemens.com>:

> > -----Original Message-----
> > From: isar-users@googlegroups.com <isar-users@googlegroups.com> On
> > Behalf Of Anton Mikanovich
> > Sent: Saturday, May 14, 2022 4:06 PM
> > To: Kiszka, Jan (T CED) <jan.kiszka@siemens.com>; isar-users <isar-
> > users@googlegroups.com>  
> > Cc: Storm, Christian (T CED SES-DE) <christian.storm@siemens.com>
> > Subject: Re: [PATCH] expand-on-first-boot: Add support for
> > devicemapper
> > 
> > 21.04.2022 20:10, Jan Kiszka wrote:  
> > > From: Jan Kiszka <jan.kiszka@siemens.com>
> > >
> > > When the rootfs is inside a devicemapper volume, e.g. dm-verity,
> > > the script so far fails to identify the boot device. This adds at
> > > least basic support for that case (single level, single slave).
> > > Once there is a good example for more complex setups, this could
> > > be taken into account as well.
> > >
> > > Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>  
> > 
> > Applied to next, thanks.  
> 
> This patch breaks very simple partition layouts like the following:
> 
> $> mount | grep sda  
> /dev/sda2 on / type ext4 (rw,relatime)
> /dev/sda1 on /boot type vfat
> (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
> 
> With this layout, the service fails with the following error:
> Boot device equals root device - no partitioning found
> 
> @Jan: It looks like the check of the device slaves is not sane.
> Could you please have a second look and try to fix it?
> 
> It also makes me wonder why the CI did not find it.

I think expand is not covered in any of our CI configs. We currently
have Tobias working on systemd growfs and repart, and might see more
testing coming with his patches. Hopefully including also a "qemu-img
convert resize" to see it grow and possibly check that it really did.

Henning

> Felix
> 
> > 
> > --
> > You received this message because you are subscribed to the Google
> > Groups "isar-users" group.
> > To unsubscribe from this group and stop receiving emails from it,
> > send an email to isar-users+unsubscribe@googlegroups.com.
> > To view this discussion on the web visit
> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.g
> > oogle.com%2Fd%2Fmsgid%2Fisar-users%2Fa016bb05-21c1-e179-68cc-
> > f1d96311e210%2540ilbers.de&amp;data=05%7C01%7Cfelix.moessbauer%40sie
> > mens.com%7Ce400a882e3df426ed81508da35b2d6e4%7C38ae3bcd95794fd4ad
> > dab42e1495d55a%7C1%7C0%7C637881340185739960%7CUnknown%7CTWFpb
> > GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M
> > n0%3D%7C2000%7C%7C%7C&amp;sdata=SKokXmDUdxOGDDRMs4pn4VUu4bv
> > WO5iDgl%2BwBWT2lsI%3D&amp;reserved=0.  
> 


      reply	other threads:[~2022-05-19 12:23 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
2022-05-14 14:05 ` Anton Mikanovich
2022-05-19 11:51   ` Moessbauer, Felix
2022-05-19 12:23     ` Henning Schild [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=20220519142304.3326743e@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=christian.storm@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@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