All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Markus Baertschi" <markus@markus.org>
To: "linux-lvm@sistina.com" <linux-lvm@sistina.com>
Subject: Re: [linux-lvm] Devices seen twice - how does LVM handle ?
Date: Wed Sep 10 11:29:02 2003	[thread overview]
Message-ID: <E19x7pQ-0006HO-Q5@server2.hostpoint.ch> (raw)
In-Reply-To: <20030910132010.GC10632@percy.comedia.it>

Hi Luca,

On Wed, 10 Sep 2003 15:20:11 +0200, Luca Berra wrote:
>>However, does LVM handles this situation (disks visible twice) nicely ?
>does not seem broken to me if you have two hba.
>lvm does not support multipath

What does LVM do if it sees two paths (/dev/sdx1 entries) to the same
virtual disk ?

>>or should I continue to use my workaround (pull a fiber) to make sure
>>the disks are visible only once ?
>it is not a nice workaround.

Yes, but the only one I got to work in the timeframe I had to get the
machines up and running again.

>>- Are there risks of corruption ?
>i don't think so.
Why ?

>>- What happens if the path the LVM happens to use breaks, but the other
>>is still up. Will LVM handle fail-over ?
>lvm does not support multipath
OK.

>at the moment your best chance is setting up an md multipath
>and building your lvm over the md devices. be sure to use mdadm instead
>of raidtools to manage the md.

I'm not familiar with md. The volumes are already there and in production,
If possible I don't want to reconfigure (downtime...).

>i have this setup (2 hbas to same storage with lvm over md multipath) in
>production, and it works fine.
>another option could be if your hba driver handles multipath. i know
>some qlogic boards do.

I'm using qlogic boards with the qla2300 failover driver. This was working
perfectly until someone installed a blade center on unrelated ports
of the same storage box and changed the WWN of the box in the process.
The linux servers were rebooted three months (!) later for an unrelated
purpose and promptly failed to come up (vgscan segfault...). The failover
driver now thinks we have two storage boxes...

In the short run the only solution I had was to remove one path/fiber.

The real fix is to reconfigure the storage box, but this has to be done
when I can stop all servers connected to it (sunday 02:00 AM...).

In the meantime I installed the latest LVM and this fixes the segfault
problem. My main priority is stability right now and I prefer running
on one fiber than in a potentially dangerous configuration. The fiber
can be switched in a hurry (just plug in the other one), software needs
skills the local people don't have (I'm most of the time not on site).

Markus


--
  Markus Baertschi             Phone: ++41 (21) 807 1677
  Bas du Rossé 14b             Fax  : ++41 (21) 807 1678
  CH-1163, Etoy                Email: markus@markus.org
  Switzerland                  Homepage: www.markus.org

  reply	other threads:[~2003-09-10 11:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10  6:49 [linux-lvm] Can't install LVM 1.0.7 on Redhat Advanced Server 2.1 Please help Gene
2003-09-10  8:05 ` [linux-lvm] Devices seen twice - how does LVM handle ? Markus Baertschi
2003-09-10  8:21   ` Luca Berra
2003-09-10 11:29     ` Markus Baertschi [this message]
2003-09-10 11:58     ` Rainer Krienke
2003-09-10 13:24       ` Markus Baertschi
2003-09-10  8:15 ` [linux-lvm] Can't install LVM 1.0.7 on Redhat Advanced Server 2.1 Please help Luca Berra
2003-09-10  8:30   ` Gene

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=E19x7pQ-0006HO-Q5@server2.hostpoint.ch \
    --to=markus@markus.org \
    --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 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.