From: Franc Carter <franc@tech.sirca.org.au>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM Multi Path Support
Date: Thu Mar 4 19:11:08 2004 [thread overview]
Message-ID: <200403051112.38529.franc@tech.sirca.org.au> (raw)
In-Reply-To: <20040304093054.GS662@reti>
Hi,
I have a related question.
I have just set up LVM on the LUNS from a HDS-9570 with a
qla-2300 driver in failover mode. This results in each
LUN being exposed to the operating system twice, once for
each controller. However when a controller fails the
card transparently maps the requests to the secondary
controller so that the original scsi target still works.
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.
I'd like to know if this is just good luck, or if it's behaviour
I can rely ?
thanks
On Thursday 04 March 2004 20:30, Joe Thornber wrote:
> On Wed, Mar 03, 2004 at 04:03:49PM -0300, Eduardo Dias wrote:
> > Dear All,
> >
> > I would like to know if LVM Linux has (or will) support to multi path
links?
>
> There is a v. old patch kicking around that adds some sort of multipath
> support to LVM1. Search this list to find it. It hasn't ever been
> part of an official release.
>
> LVM2 doesn't support multipath but we're currently developing a
> multipath target for device-mapper, and Christophe Varoqui is writing
> a standalone userland tool to drive it. The current thinking is that
> the LVM2 tools will just use the devices that Christophes tool
> creates.
>
> - Joe
>
> _______________________________________________
> 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/
>
>
--
Franc Carter Ph:61-2-8374-5071 Fax: 61-2-8374-5070
Systems Manager, SIRCA Ltd http://www.sirca.org.au/
DISCLAIMER: The contents of this email, inclusive of attachments, may
be legally privileged and confidential. Any unauthorised use of the
contents is expressly prohibited. If you have received this message in
error or are not the intended recipient, you should destroy the email
message along with any attachment(s). Unintended recipients of this
email are prohibited from retaining, disclosing, distributing or using
any information contained herein. This email is also subject to
copyright. No part of it should be reproduced, adapted or transmitted
without the written consent of the copyright owner.
next prev parent reply other threads:[~2004-03-05 0:13 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 [this message]
2004-03-05 4:05 ` Joe Thornber
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=200403051112.38529.franc@tech.sirca.org.au \
--to=franc@tech.sirca.org.au \
--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.