From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: isar-users@googlegroups.com
Cc: henning.schild@siemens.com,
Joe MacDonald <joe_macdonald@mentor.com>,
"Moessbauer, Felix" <felix.moessbauer@siemens.com>
Subject: Re: [PATCH v5 1/6] expand-on-first-boot: really only do that once, especially on failure
Date: Thu, 15 Dec 2022 16:32:46 +0100 [thread overview]
Message-ID: <CAJGKYO7ab6sb4t2jZhGovKGcr4V+GtYpkMsXHbBNrSj5QYyYCg@mail.gmail.com> (raw)
In-Reply-To: <20221215142759.26327-2-henning.schild@siemens.com>
On Thu, 15 Dec 2022 at 15:28, <henning.schild@siemens.com> wrote:
>
> From: Henning Schild <henning.schild@siemens.com>
>
> We do hope the expand will work but we also know very well that it can
> fail. The script is written in a way that currently only supports one
> try. And not a retry if it failed in an earlier boot.
> So make sure to disable the service also on failure.
Disabling the expansion of last partition service at the first failure:
- decreases the chance that the human operator will notice the failure
in the boot logs and thus create a barrier to investigate that failure
and/or report it promptly.
- it is not compatible with the case of an unsupervised embedded
system that should not be able to go in service unless it is provided
with the full storage space.
- does not solve any real problem but just masquerading any related
issue and limits the options above.
My suggestion is to not apply this patch. I did a test and without
this patch the service continues to be active unless it completes
successfully.
I hope this helps, R-
next prev parent reply other threads:[~2022-12-15 15:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 14:27 [PATCH v5 0/6] expand-on-first-boot btrfs and CI testing henning.schild
2022-12-15 14:27 ` [PATCH v5 1/6] expand-on-first-boot: really only do that once, especially on failure henning.schild
2022-12-15 15:32 ` Roberto A. Foglietta [this message]
2022-12-15 14:27 ` [PATCH v5 2/6] expand-on-first-boot: support resizing a btrfs henning.schild
2022-12-15 17:48 ` Roberto A. Foglietta
2022-12-15 14:27 ` [PATCH v5 3/6] meta-isar: introduce an example to use btrfs henning.schild
2022-12-15 14:27 ` [PATCH v5 4/6] CI: improve cibuilder readability henning.schild
2022-12-15 14:27 ` [PATCH v5 5/6] meta-isar: install expand-on-first-boot in most images and add space henning.schild
2022-12-15 14:27 ` [PATCH v5 6/6] CI: expect a message about filesystem resize vom expand script 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=CAJGKYO7ab6sb4t2jZhGovKGcr4V+GtYpkMsXHbBNrSj5QYyYCg@mail.gmail.com \
--to=roberto.foglietta@gmail.com \
--cc=felix.moessbauer@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=joe_macdonald@mentor.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