archive mirror
 help / color / mirror / Atom feed
From: Marian Csontos <>
Subject: Re: [linux-lvm] LVM PV UUID problem
Date: Mon, 12 Oct 2020 12:57:06 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20201009153924.GC13687@IUPUI.Edu>

On 10/9/20 5:39 PM, Mark H. Wood wrote:
> On Fri, Oct 09, 2020 at 11:18:38AM -0400, Digimer wrote:
>> On 2020-10-09 10:43 a.m., Zdenek Kabelac wrote:
>>> Dne 09. 10. 20 v 15:12 Digimer napsal(a):
>>>> Hi all,
>>>>  �� I'm storing LVM information in a postgres database, and wanted to use
>>>> the UUID from the PVs / VGs / LVs as the UUIDs in the database. I
>>>> noticed when I tried to do this that postgres complained that the UUID
>>>> was not valid. I checked with an online UUID validator
>>>> ( and it also
>>>> reported as invalid.
>>>> Example;
>>>> ====
>>>> # pvdisplay | grep UUID
>>>>  �� PV UUID�������������� jLkli2-dEXx-5Y8n-pYlw-nCcy-9dFL-3B6jU3
>>>> ====
>>>>  �� Is this a known issue?
>>> Hi
>>> At the time of lvm2 devel I believe UUID was just a unique identifier,
>>> later some effort to standardize it came in.
>>> But really you should NOT be using basically internal unique identifiers
>>> in your DB - this are internal to DM/LVM work and might be changed at
>>> any time to something else.
>>> User is supposed to use� 'vgname' & 'lvname'� - so there you can put those
>>> valid UUID sequences - although human readable strings are always nicer ;)
>>> Zdenek
>> The trick is that VG and LV names can change, so I wanted to use the
>> (so-called) UUID as a way to keep track of a given item through name
>> changes.
>> I suppose I'll have to rework to use the internal "UUIDs" as more like
>> serial numbers instead...
> Well, if we are stuck with non-standard "UUID"s, at least they are
> meant to be Universally Unique, so they can be treated as unique
> opaque string tokens.  Or you might find a library function that can
> return the unencoded binary value and you can encode it as you please.
> However, the issue of persistence remains.
> FWIW I think it's quite reasonable for someone to want immutable
> unique identifiers for distinct objects such as LVM PVs, especially
> when the "unique identifier" part is already available and quite
> visible.

...and then there is lvconvert which takes existing LV and creates a new 
object with the same name, and original LV is used as a "compnent" (e.g. 
raid1 leg, or snapshot origin)

So now there are two objects, one with the same name, and other one - 
the original LV, which one should use the original UUID?

Just consider LVM UUIDs as MUST BE unique IDs.

Or better MUST BE for lvm to work properly, and SHOULD BE in reality (as 
duplicates occur e.g. when SAN snapshots are visible to the system and 
you run into troubles, and so there are filters,...)

-- Martian

> _______________________________________________
> linux-lvm mailing list
> read the LVM HOW-TO at

      reply	other threads:[~2020-10-12 10:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09 13:12 [linux-lvm] LVM PV UUID problem Digimer
2020-10-09 14:43 ` Zdenek Kabelac
2020-10-09 15:18   ` Digimer
2020-10-09 15:39     ` Mark H. Wood
2020-10-12 10:57       ` Marian Csontos [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).