public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com, "Schmidl,
	Tobias" <tobiasschmidl@siemens.com>
Subject: Re: [PATCH 1/1] expand last partition supports btrfs
Date: Fri, 30 Sep 2022 13:29:52 +0200	[thread overview]
Message-ID: <CAJGKYO5Y3pLDYOW9U+6CHvG3B3QbD-SSidtYXZV3SFBsztj1hw@mail.gmail.com> (raw)
In-Reply-To: <20220930125812.312b8dcc@md1za8fc.ad001.siemens.net>

[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]

Il Ven 30 Set 2022, 12:58 Henning Schild <henning.schild@siemens.com> ha
scritto:

> Am Fri, 30 Sep 2022 09:43:23 +0200
> schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:
>
> > Hi,
> >
> >  the patch is in attachment, I am sorry. However, it has been created
> > with git format-patch as requested by contributions rules.
> >
> >  This patch extend the last partition to btrfs because only ext4 was
> > supported.
>
> We had a similar patch floating around, but as already mentioned our
> current understanding is that systemd-resizefs will be the way forward.
>
> So this patch should not be merged while we still hold on to that idea
> and wait for that systemd patch to arrive and cover the one corner-case
> it still leaves open.
>

Is the btrfs a corner case? ;-)

It is OK do not let go it into the mainstream. After all the btrfs is less
performant than ext4 but it has a data corruption feature that cannot allow
corrupted data to be read. It might worth a consideration in some
fields/applications.

It has been designed just to be a transitional quick-patch.

Thanks for your opinion and feedback, R-

[-- Attachment #2: Type: text/html, Size: 1943 bytes --]

  reply	other threads:[~2022-09-30 11:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AM0PR10MB2020D00D6BBFAA81427A64A6AA569@AM0PR10MB2020.EURPRD10.PROD.OUTLOOK.COM>
2022-09-30  7:43 ` Roberto A. Foglietta
2022-09-30 10:58   ` Henning Schild
2022-09-30 11:29     ` Roberto A. Foglietta [this message]
2022-09-30 11:42       ` Henning Schild
2022-09-30 17:37         ` Roberto A. Foglietta
2022-09-30 18:25           ` Henning Schild
2022-10-01 14:35             ` Roberto A. Foglietta
2022-10-04 22:16         ` 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=CAJGKYO5Y3pLDYOW9U+6CHvG3B3QbD-SSidtYXZV3SFBsztj1hw@mail.gmail.com \
    --to=roberto.foglietta@gmail.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.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