Linux LVM users
 help / color / mirror / Atom feed
From: Matt Schillinger <mschilli@vss.fsi.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] UUID
Date: Thu Jan  9 16:34:01 2003	[thread overview]
Message-ID: <1042151798.18166.271.camel@mosix> (raw)

Can someone explain the UUID, etc  on a volume and on VGs?

Is the UUID stored on the volume, or on the host machine?

The reason I ask, is that I have a parrallel scsi raid, which is
connected to 2 machines.  If i reboot both machines, or go through a
vgexport/import procedure (while online), i can see the VGs and LVs on
both machines.. can even mount the volumes simultaneously (It was only a
test.. I understand that it is not a Shared Filesystem, and would never
do simultaneous mounts on production filesystems). 

This is what I believe to be the case:

1. The UUID is stored on the volume itself, and the VG data is stored
somewhere on the disks also.
2. The import/export/activated/deactivated status of a volume is held on
the host machine.

this allows 2 machines to see the same VG/LVs. 

Is this correct?  And is it supported as a function of LVM, or am I in
'unsupported' territory?


-- 
Matt Schillinger
mschilli@vss.fsi.com

                 reply	other threads:[~2003-01-09 16:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1042151798.18166.271.camel@mosix \
    --to=mschilli@vss.fsi.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox