Re: [linux-lvm] logical volume usage type code, equivalent to GPT partition type GUID

2021-11-03 Thread David Teigland
On Wed, Nov 03, 2021 at 01:44:33PM -0400, Chris Murphy wrote: > 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

Re: [linux-lvm] logical volume usage type code, equivalent to GPT partition type GUID

2021-11-03 Thread Roger Heflin
You have some basic problems. #1 with shared lvm you would need a way to tell where it should go, so you would have to have a mount_hostname type data in logical_volumes sections. #2 you would also need a mount_point entry, and a mount_opts entry. And then at the end you are basically moving

[linux-lvm] logical volume usage type code, equivalent to GPT partition type GUID

2021-11-03 Thread Chris Murphy
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