Linux LVM users
 help / color / mirror / Atom feed
From: Fabian Herschel <fabian.herschel@suse.de>
To: linux-lvm@sistina.com, lvm@interlinx.bc.ca
Subject: Re: [linux-lvm] Two drives with the same UUID
Date: Mon Jan 13 05:05:02 2003	[thread overview]
Message-ID: <03011311575101.01471@grimsel> (raw)
In-Reply-To: <20030110213858.GI3393@pc.ilinx>

On Friday 10 January 2003 22:38, lvm@interlinx.bc.ca wrote:
> If I had a system with a functional LVM configuration (1.0.6ish) and I
> were to "duplicate" the drive in it (i.e. dd if=/dev/sda of=/dev/sdb)
> and then try to boot that system (with both drives installed and
> functional), what would happen?
>
> Of course, because I am asking, I have tried it.  :-)  During boot LVM
> failed to find any logical volumes.  Is this expected?  It's not
> surprising mind you, but I wonder how it was designed to deal with
> this situation.

Sorry, but this is a normal reaction of the logical volume manager. Why?
Each "normal" volume manager uses a special part of the disk device (or a
special part of a partition) to identify the physical media. If you copy the
complete disk, you also copy this unique identifier. So LVM get confused
to find a media twice.

Best regards
Fabian Herschel
>
> b.

----------------------------------------
Content-Type: application/pgp-signature; charset="us-ascii"; 
name="Attachment: 1"
Content-Transfer-Encoding: 7bit
Content-Description: 
----------------------------------------

-- 
<Fabian.Herschel@suse.de>
SuSE Linux AG * Mergenthalerallee 45-47 * D-65760 Eschborn
Tel: +49-6196-50951-23 * Fax: +49-6196-409-607
http://www.suse.de * Alice Homepage: http://www.suse.de/~fabian

      reply	other threads:[~2003-01-13  5:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-10 15:38 [linux-lvm] Two drives with the same UUID lvm
2003-01-13  5:05 ` Fabian Herschel [this message]

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=03011311575101.01471@grimsel \
    --to=fabian.herschel@suse.de \
    --cc=linux-lvm@sistina.com \
    --cc=lvm@interlinx.bc.ca \
    /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