Same in concept, different implementation, easier to use? The Lustre does the same thing: It has what it calls UUID's, that are actually more descriptive strings than what the standard calls for. On Thu, 2004-09-23 at 01:47, Ralf S. Engelschall wrote: > 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 > > _______________________________________________ > linux-lvm mailing list > linux-lvm@redhat.com > https://www.redhat.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ -- Dan Stromberg DCS/NACS/UCI <strombrg@dcs.nac.uci.edu>
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
