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: [linux-lvm] Devices seen twice - how does LVM handle ?
Date: Wed Sep 10 08:05:01 2003	[thread overview]
Message-ID: <E19x4eC-0008Oa-VB@server2.hostpoint.ch> (raw)
In-Reply-To: <20030910114840.13991.qmail@web42002.mail.yahoo.com>

For reasons too complicate to explain here our SAN configuration is
broken. The effect is that linux sees the san disks twice. The originally
installed 'vgscan' was responding with a segfault to this situation.
After the installation of the latest release (1.0.7) vgscan is fine
and the volumegroup comes up.

However, does LVM handles this situation (disks visible twice) nicely ?
or should I continue to use my workaround (pull a fiber) to make sure
the disks are visible only once ?
- Are there risks of corruption ?
- What happens if the path the LVM happens to use breaks, but the other
is still up. Will LVM handle fail-over ?

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  8:05 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 ` Markus Baertschi [this message]
2003-09-10  8:21   ` [linux-lvm] Devices seen twice - how does LVM handle ? Luca Berra
2003-09-10 11:29     ` Markus Baertschi
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=E19x4eC-0008Oa-VB@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.