Linux LVM users
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM with multi-path disks?
Date: Sun, 5 Aug 2001 09:58:11 +0200	[thread overview]
Message-ID: <20010805095811.A4626@colombina.comedia.it> (raw)
In-Reply-To: <20010805003257.A2728@glines.org>; from mark@glines.org on Sun, Aug 05, 2001 at 12:32:57AM -0700

On Sun, Aug 05, 2001 at 12:32:57AM -0700, Mark Glines wrote:
> On Sun, Aug 05, 2001 at 09:12:01AM +0200, Luca Berra wrote:
> > there is an (*horrible*) piece of code in pv_read_all_pv.c
> > that deals with multiple entries for the same PV, so all duplicate
> > PV are skipped, so the md will be the obly one detected.
> > what probably happened to John is, that his PV was killed by
> > this routine (they were duplicate and not md devices)
> 
> I would only think this is a problem when md isn't being used.  In the
> above described situation, vgscan would see 2 devices which have md
> headers (and ignore them), and one LVM signature (and use it)?

Correct!

> If the code does what you say, and LVM was using the dual-path SCSI
> device directly, then it would detect one and ignore the other, and it
> would still work as if there was only one route to the drive.

this is also correct, i was just guessing there might be another dragon
in this code, but we would need an output of vgscan -d from John to check.

> However, in this case, md is in the middle, and its md's job to handle
> multi-path.  LVM should be ignoring md's lowlevel volumes anyway, and
> act solely on the virtual device md exports.  Am I missing something?
John is not using md yet, you are correct in all you say.

Regards,
L.
-- 
Luca Berra -- bluca@comedia.it
        Communication Media & Services S.r.l.
 /"\
 \ /     ASCII RIBBON CAMPAIGN
  X        AGAINST HTML MAIL
 / \

  reply	other threads:[~2001-08-05  7:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-03 23:16 [linux-lvm] LVM with multi-path disks? John DeFranco
2001-08-04 15:40 ` Luca Berra
2001-08-05  0:28   ` Ragnar Kjørstad
2001-08-05  7:12     ` Luca Berra
2001-08-05  7:32       ` Mark Glines
2001-08-05  7:58         ` Luca Berra [this message]
2001-08-05 17:44           ` John DeFranco
2001-08-05 18:25             ` Luca Berra
2001-08-05 18:48               ` Michael Lausch
2001-08-05 21:47               ` Ragnar Kjørstad
2001-08-06 17:01                 ` John DeFranco
2001-08-06 17:26                   ` Ragnar Kjørstad
2001-08-07  1:46                 ` Tracy R Reed
2001-08-07  5:23                   ` Ragnar Kjørstad
2001-08-07  5:38                     ` Carlo Marcelo Arenas Belon
2001-08-07  7:41                       ` Tracy R Reed
2001-08-07  7:37                     ` Tracy R Reed
2001-08-07  8:58                     ` Joe Thornber
2001-08-05  9:06     ` Christoph Hellwig
2001-08-05 21:47       ` Ragnar Kjørstad
2001-08-05 22:41         ` Christoph Hellwig
2001-08-06  1:20 ` AJ Lewis
  -- strict thread matches above, loose matches on Subject: below --
2001-08-06 18:02 Gonyou, Austin
2001-08-07 16:30 Gonyou, Austin

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=20010805095811.A4626@colombina.comedia.it \
    --to=bluca@comedia.it \
    --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