From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: "Schmidl, Tobias" <tobiasschmidl@siemens.com>
Cc: isar-users@googlegroups.com, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH 1/1] expand last partition supports btrfs (inline test)
Date: Fri, 30 Sep 2022 12:39:01 +0200 [thread overview]
Message-ID: <CAJGKYO7uDQNo=t9Wsv4-LKXqx6jF6C9UvA3LvKAsMM45-aN+BQ@mail.gmail.com> (raw)
In-Reply-To: <7173fe9ca22bb8f50ba6c941fb62b1799f066e5d.camel@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 1561 bytes --]
Il Ven 30 Set 2022, 12:23 Schmidl, Tobias <tobiasschmidl@siemens.com> ha
scritto:
> Hi Jan, Roberto,
>
> Am Freitag, dem 30.09.2022 um 10:56 +0200 schrieb Jan Kiszka:
> > On 30.09.22 10:00, Roberto A. Foglietta wrote:
> >
> >
> >
> https://groups.google.com/d/msgid/isar-users/20220630135531.717696-2-tobiasschmidl%40siemens.com>
> is the way forward, but it needs some more fine-tuning. Tobias, what is
> > the status there?
> >
>
> As I understand it the mentioned patch is dead, since the systemd version
> in stretch is too old for systemd-resizefs - or did I miss anything?
>
Hi Tobias and Jan,
as you can see my approach is straight simple: if extending the ext4 fails
because it does not match the filesystem type then try with btrfs tool.
Obviously, the btrfs tool is added as dependencies among others before
defined.
pro: it supports btrfs, easy to catch
contro: not a general approach
I tend to be very pragmatic: the current supports ext4 resize only + a
simple patch it supports btrfs also. This is an improvement and add a
little of complexity. May be tomorrow, it will arrive the support for xfs
or dm-crypto. Step by step functionalities will be added and at a certain
point someone will feel the nessecity to rationalise the code but not
necessarily generalising (architecture change).
This kind of development is about natural evolution rather than
intelligent design. Ok, sometimes it is necessary to reorganise, rewrite,
generalise, the product of the natural evolution but usually fits enough.
My 2 cents, IMHO.
Cheers, R.
>
[-- Attachment #2: Type: text/html, Size: 2533 bytes --]
next prev parent reply other threads:[~2022-09-30 10:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 8:00 Roberto A. Foglietta
2022-09-30 8:56 ` Jan Kiszka
2022-09-30 10:23 ` Schmidl, Tobias
2022-09-30 10:39 ` Roberto A. Foglietta [this message]
2022-09-30 10:50 ` Bezdeka, Florian
2022-09-30 11:09 ` Roberto A. Foglietta
2022-09-30 11:17 ` Roberto A. Foglietta
2022-09-30 10:51 ` Henning Schild
2022-09-30 11:34 ` Fwd: [PATCH 1/1] expand last partition supports btrfs (inline 2nd version) Roberto A. Foglietta
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='CAJGKYO7uDQNo=t9Wsv4-LKXqx6jF6C9UvA3LvKAsMM45-aN+BQ@mail.gmail.com' \
--to=roberto.foglietta@gmail.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