From: Digimer <lists@alteeve.ca>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM PV UUID problem
Date: Fri, 9 Oct 2020 09:12:38 -0400 [thread overview]
Message-ID: <fee58e48-151f-9eab-a6a2-eb31c690029c@alteeve.ca> (raw)
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?
Thanks for any help/insight!
--
Digimer
Papers and Projects: https://alteeve.com/w/
"I am, somehow, less interested in the weight and convolutions of
Einstein’s brain than in the near certainty that people of equal talent
have lived and died in cotton fields and sweatshops." - Stephen Jay Gould
next reply other threads:[~2020-10-09 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 13:12 Digimer [this message]
2020-10-09 14:43 ` [linux-lvm] LVM PV UUID problem Zdenek Kabelac
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=fee58e48-151f-9eab-a6a2-eb31c690029c@alteeve.ca \
--to=lists@alteeve.ca \
--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).