From: Chris Murphy <lists@colorremedies.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] logical volume usage type code, equivalent to GPT partition type GUID
Date: Wed, 3 Nov 2021 13:44:33 -0400 [thread overview]
Message-ID: <CAJCQCtRCEtGmsVQt0ug4c6PxGXkwhHjtrppNPSxa0StYs08mQA@mail.gmail.com> (raw)
Hi,
I'm wondering to what degree the current LVM metadata format(s) can
support additional or even arbitrary metadata.
The UEFI spec defines the GPT, and GPT defines a "partition type GUID"
for each partition to define it's usage/purpose, in rather open ended
fashion. I'm wondering about an equivalent for this with LVM, whether
it's useful and how difficult it would be to implement. This is all
very hypothetical right now, so a high level discussion is preferred.
The starting point is the Discoverable Partitions Spec:
http://systemd.io/DISCOVERABLE_PARTITIONS/
Where GPT partition type codes are used to discover file systems, and
their intended use without having to explicitly place them into
/etc/fstab for startup time discovery and mounting. But LVM doesn't
have an equivalent for exposing such a capability, because it implies
many volumes within the larger pool and also the pool might comprise
many devices.
The same problem exists for Btrfs subvolumes, and ZFS datasets.
What might be possible and what is definitely not possible, is what
I'm interested in understanding for now.
Thanks,
--
Chris Murphy
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next reply other threads:[~2021-11-03 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 17:44 Chris Murphy [this message]
2021-11-03 18:21 ` [linux-lvm] logical volume usage type code, equivalent to GPT partition type GUID Roger Heflin
2021-11-03 20:15 ` David Teigland
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=CAJCQCtRCEtGmsVQt0ug4c6PxGXkwhHjtrppNPSxa0StYs08mQA@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=linux-lvm@redhat.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).