linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Mark H. Wood" <mwood@iupui.edu>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM PV UUID problem
Date: Fri, 9 Oct 2020 11:39:24 -0400	[thread overview]
Message-ID: <20201009153924.GC13687@IUPUI.Edu> (raw)
In-Reply-To: <b3d53a4d-dafe-4d92-700a-f9df28061020@alteeve.ca>

[-- Attachment #1: Type: text/plain, Size: 2286 bytes --]

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

-- 
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2020-10-09 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09 13:12 Digimer
2020-10-09 14:43 ` Zdenek Kabelac
2020-10-09 15:18   ` Digimer
2020-10-09 15:39     ` Mark H. Wood [this message]
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=20201009153924.GC13687@IUPUI.Edu \
    --to=mwood@iupui.edu \
    --cc=linux-lvm@redhat.com \
    --subject='Re: [linux-lvm] LVM PV UUID problem' \
    /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

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