All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ralf S. Engelschall" <rse@engelschall.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM UUIDs are not UUIDs!?
Date: Thu, 23 Sep 2004 10:47:41 +0200	[thread overview]
Message-ID: <20040923084741.GA5658@engelschall.com> (raw)

While setting up an LVM2 based 3TB storage the last days I've stumbled
over LVM2's "UUID" strings as displayed by its pvdisplay, vgdisplay, and
lvdisplay commands. It is clear that LVM2 requires those ids, but *WHY*
are they called "UUID"?

They do NOT conform in any way to the standardized ISO/IEC 11578:1996
compliant Universally Unique Identifier (UUID) strings. Neither by the
way they are created (LVM2 UUIDs are just random numbers while ISO v4
random UUIDs are fixed bit-fields plus random remaining bits) nor the
way they are formatted. Examples:

LVM2               UUID: H9C8iE-braW-70bk-Fx9x-lMIX-Rmmy-5XgkM9
ISO/IEC 11578:1996 UUID: 4a8287f4-0d33-11d9-8068-0002b31abd79

So, wouldn't it be reasonable that either LVM2 uses a real open-source
UUID library for dealing with standardized UUIDs (ext2fs's libuuid, OSSP
uuid, etc) or at least names its ids own id strings just "ID" or even
"LVMID"?

Perhaps at least in the visible output strings in order to reduce
confusion with standardized UUIDs...

                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com

             reply	other threads:[~2004-09-23  8:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-23  8:47 Ralf S. Engelschall [this message]
2004-09-23 17:10 ` [linux-lvm] LVM UUIDs are not UUIDs!? Dan Stromberg
2004-09-23 17:53   ` Ralf S. Engelschall
2004-09-25 16:41     ` Alasdair G Kergon

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=20040923084741.GA5658@engelschall.com \
    --to=rse@engelschall.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.