From: Joe Thornber <thornber@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM Multi Path Support
Date: Fri Mar 5 04:05:00 2004 [thread overview]
Message-ID: <20040305090741.GD744@reti> (raw)
In-Reply-To: <200403051112.38529.franc@tech.sirca.org.au>
On Fri, Mar 05, 2004 at 11:12:38AM +1100, Franc Carter wrote:
> LVM appears to do the 'right thing for me' in that it recognises
> that the the two PVs are one (I assume via the UUID) and ignore
> the second LUN.
Yes, LVM writes a label to the start of a PV to identify it.
> I'd like to know if this is just good luck, or if it's behaviour
> I can rely ?
I don't think it's defined which of the 2 devices LVM will choose,
does this matter ? If so you could always set up a filter in lvm.conf
to remove one (probably advisable anyway).
- Joe
next prev parent reply other threads:[~2004-03-05 9:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 17:33 [linux-lvm] LVM Multi Path Support Eduardo Dias
2004-03-04 4:28 ` Joe Thornber
2004-03-04 19:11 ` Franc Carter
2004-03-05 4:05 ` Joe Thornber [this message]
2004-03-05 16:35 ` Franc Carter
2004-03-08 4:29 ` Joe Thornber
2004-03-08 7:08 ` Markus Baertschi
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=20040305090741.GD744@reti \
--to=thornber@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox