public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "T. Schaffner" <tobias.schaffner@siemens.com>
To: <isar-users@googlegroups.com>
Cc: <henning.schild@siemens.com>,
	Tobias Schaffner <tobias.schaffner@siemens.com>
Subject: [PATCH 0/2] expand-on-first-boot: try fs resize on expanded partitions
Date: Tue, 8 Nov 2022 12:28:35 +0100	[thread overview]
Message-ID: <20221108112837.435213-1-tobias.schaffner@siemens.com> (raw)

From: Tobias Schaffner <tobias.schaffner@siemens.com>

If the filesystem resize on first boot fails or gets interrupted the service
will not be disabled. But when the script is called on the next boot it will
not try to expand the filesystem as the partition is already expanded.

Check if the partition has to be expanded before expanding it but always try
to resize the filesystem. Leave the decision if the filesystem has to be resized
to the used tool.

Improve the check if we have to expand the partition by calculating the last
usabe block in the GUID table.

Tobias Schaffner (2):
  Check if last partition ends at GPT backup header
  Always try resizing the fs in expand on first boot

 .../files/expand-last-partition.sh            | 54 +++++++++----------
 1 file changed, 25 insertions(+), 29 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-11-08 11:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 11:28 T. Schaffner [this message]
2022-11-08 11:28 ` [PATCH 1/2] Check if last partition ends at GPT backup header T. Schaffner
2022-11-09  8:26   ` Henning Schild
2022-11-09  9:40     ` Schaffner, Tobias
2022-11-09 14:54       ` Henning Schild
2022-11-08 11:28 ` [PATCH 2/2] Always try resizing the fs in expand on first boot T. Schaffner
2022-11-09  8:52   ` Henning Schild
2022-11-09 10:11     ` Schaffner, Tobias

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=20221108112837.435213-1-tobias.schaffner@siemens.com \
    --to=tobias.schaffner@siemens.com \
    --cc=henning.schild@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