All of lore.kernel.org
 help / color / mirror / Atom feed
From: Navindra Umanee <navindra@cs.mcgill.ca>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] setting VG UUID
Date: Thu Jan  8 16:35:01 2004	[thread overview]
Message-ID: <20040108163409.A3963@cs.mcgill.ca> (raw)
In-Reply-To: <20040108212542.GF23918@homer.msp.redhat.com>; from Alasdair G Kergon on Thu, Jan 08, 2004 at 03:25:42PM -0600

Alasdair G Kergon <agk@redhat.com> wrote:
> > So much for universal uniqueness...
> The VG UUIDs *are* meant to all be the same on devices that are part of the
> same VG.  It's the PV UUIDs that differ.

Oh, I realise that.  Just a small joke about my non-random choice of
UUID... :)

> > For the record, I created my LVM1 partitions with Linux Mandrake 9.2.
> Could /dev/urandom have been missing when pvcreate was run?
> We think that would explain the symptoms.

Good thought!  It's very possible since of course only a crippled
environment is available at install time.  I'll try to verify it
later.

> > Should "vgchange -a n" maybe clean up these symlinks?
> It's supposed to do.

Hmmm.  I've hacked my init scripts to do it in the meanwhile, but I
will pay closer attention to what happens next time I boot and report
back.

Happily, so far I don't see any reason to go back to Linux 2.4 though
and a quite a few reasons to stay in 2.6....

Cheers,
Navin.

  reply	other threads:[~2004-01-08 16:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07  6:00 [linux-lvm] setting VG UUID Navindra Umanee
2004-01-07  8:26 ` Navindra Umanee
2004-01-08 16:27   ` Alasdair G Kergon
2004-01-08 16:35     ` Navindra Umanee [this message]
2004-03-12 17:17       ` Dan Merillat
2004-01-22 16:50 ` Luca Berra
2004-01-22 20:53   ` Navindra Umanee
2004-01-23  2:27     ` Luca Berra
2004-01-23  8:37   ` Alasdair G Kergon
2004-01-23 14:33     ` Luca Berra

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=20040108163409.A3963@cs.mcgill.ca \
    --to=navindra@cs.mcgill.ca \
    --cc=linux-lvm@sistina.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.