archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <>
To: LVM general discussion and development <>,
	Digimer <>
Subject: Re: [linux-lvm] LVM PV UUID problem
Date: Fri, 9 Oct 2020 16:43:52 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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?


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 ;)


  reply	other threads:[~2020-10-09 14:43 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 [this message]
2020-10-09 15:18   ` Digimer
2020-10-09 15:39     ` Mark H. Wood
2020-10-12 10:57       ` Marian Csontos

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