From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Digimer <lists@alteeve.ca>
Subject: Re: [linux-lvm] LVM PV UUID problem
Date: Fri, 9 Oct 2020 16:43:52 +0200 [thread overview]
Message-ID: <32651cc4-159f-a7f3-83cc-1e1c50071b93@redhat.com> (raw)
In-Reply-To: <fee58e48-151f-9eab-a6a2-eb31c690029c@alteeve.ca>
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
> (https://www.freecodeformat.com/validate-uuid-guid.php) 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
next prev parent 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:
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=32651cc4-159f-a7f3-83cc-1e1c50071b93@redhat.com \
--to=zkabelac@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=lists@alteeve.ca \
/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).