From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: Karel Zak <kzak@redhat.com>
Cc: Zdenek Kabelac <zdenek.kabelac@gmail.com>,
Michael Chang <mchang@suse.com>, Glass Su <glass.su@suse.com>,
Heming Zhao <heming.zhao@suse.com>,
"linux-lvm@lists.linux.dev" <linux-lvm@lists.linux.dev>,
grub-devel@gnu.org, util-linux@vger.kernel.org
Subject: Re: is it possible to add a new filter to detect unusable partition types
Date: Wed, 18 Dec 2024 18:05:54 +0100 [thread overview]
Message-ID: <860960db-bb66-453c-a392-1495690bb2ff@t-8ch.de> (raw)
In-Reply-To: <hdqz3hun3f5ftfwvimlopkmuujimtz5ilovkuajqesy6p4a7jd@7w6nkryhr2y7>
On 2024-12-18 15:44:45+0100, Karel Zak wrote:
> On Wed, Dec 18, 2024 at 11:12:59AM GMT, Zdenek Kabelac wrote:
[..]
> > And in the same way blkid should expose installed grub loader - currently
> > the partition with installed grub looks 'empty' with blkid....
>
> The issue I see is that boot loaders can coexist with filesystems on
> the same device. This can lead to unexpected warnings when attempting
> to view the contents of the device using mkfs tools.
Isn't this specifically about the grub second stage on GPT systems
inside a dedicated partition?
There should be no valid coexistence with a filesystem.
So having a probe in blkid looks reasonable to me.
Not that it helps in the specific case mentioned above, where everybody
is using --force anyways.
Thomas
next prev parent reply other threads:[~2024-12-18 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 8:34 is it possible to add a new filter to detect unusable partition types Heming Zhao
2024-12-17 9:13 ` Glass Su
[not found] ` <43D73CB9-32E4-405E-93A9-E985C94F4A9E__33327.0934455626$1734427189$gmane$org@suse.com>
2024-12-17 10:21 ` Zdenek Kabelac
2024-12-17 12:45 ` Michael Chang
2024-12-17 20:32 ` Demi Marie Obenour
[not found] ` <yjiu3c3e4aknayawhw7lw52kev6fvp4wm6n6wte4t27hx3fr4u__21682.4523567752$1734439545$gmane$org@cc5bu2ij2ia3>
2024-12-18 10:12 ` Zdenek Kabelac
2024-12-18 14:44 ` Karel Zak
2024-12-18 17:05 ` Thomas Weißschuh [this message]
2024-12-19 4:48 ` Michael Chang
[not found] ` <jcqrtifxjk2adtngyykvyoffh6ab3twulqra4ugq7satddqob7__49168.7655843393$1734583719$gmane$org@rngyhl7nuyhk>
2024-12-19 10:50 ` Zdenek Kabelac
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=860960db-bb66-453c-a392-1495690bb2ff@t-8ch.de \
--to=thomas@t-8ch.de \
--cc=glass.su@suse.com \
--cc=grub-devel@gnu.org \
--cc=heming.zhao@suse.com \
--cc=kzak@redhat.com \
--cc=linux-lvm@lists.linux.dev \
--cc=mchang@suse.com \
--cc=util-linux@vger.kernel.org \
--cc=zdenek.kabelac@gmail.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;
as well as URLs for NNTP newsgroup(s).