From: Ray Morris <support@bettercgi.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Duplicate PV's - how does LVM choose which one to use
Date: Tue, 21 Feb 2012 10:35:03 -0600 [thread overview]
Message-ID: <20120221103503.4ba74c70@bettercgi.com> (raw)
In-Reply-To: <20120221120933.GB12645@agk-dp.fab.redhat.com>
Perhaps when duplicates are found the seqno should be incremented
so it DOES use the same one next time, and generate a warning
indicating which one is out of date?
--
Ray Morris
support@bettercgi.com
Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/
Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/
Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php
On Tue, 21 Feb 2012 12:09:33 +0000
Alasdair G Kergon <agk@redhat.com> wrote:
> On Tue, Feb 21, 2012 at 09:40:43AM +0100, Danilo Godec wrote:
> > How does LVM decide which one to use? Will it always choose the
> > same one?
>
> You can't rely on that.
>
> I'm starting to wonder if we should add an lvm.conf option to stop
> when it sees duplicates of equal priority instead of going ahead and
> using one, and to make that the default behaviour.
>
> Alasdair
>
> _______________________________________________
> 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/
>
next prev parent reply other threads:[~2012-02-21 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 8:40 [linux-lvm] Duplicate PV's - how does LVM choose which one to use Danilo Godec
2012-02-21 12:09 ` Alasdair G Kergon
2012-02-21 16:35 ` Ray Morris [this message]
2012-02-21 16:43 ` Alasdair G Kergon
2012-02-21 16:49 ` Stuart D Gathman
2012-02-21 17:07 ` Alasdair G Kergon
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=20120221103503.4ba74c70@bettercgi.com \
--to=support@bettercgi.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 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.