From: Rob Kenna <rkenna@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM multipathing?
Date: Wed, 05 Oct 2005 09:14:28 -0400 [thread overview]
Message-ID: <4343D1B4.800@redhat.com> (raw)
In-Reply-To: <OFBC85B583.C37E7FA3-ONC3257091.0030BD40-C3257091.0030F6F9@technoserv.ru>
Coming in Update2 of RHEL 4. Release is imminent.
- rob
Pavel A Tsvetkov wrote:
>
> Hello all!
>
> Does anybody know about RedHat plan's to support multipathing (failover
> & loadbalancing) in AS 4.x LVM2 ?
>
> Thanks a lot ! Pavel
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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/
--
Robert Kenna / Red Hat
Sr Product Mgr - Storage
10 Technology Park Drive
Westford, MA 01886
o: (978) 392-2410 (x22410)
f: (978) 392-1001
c: (978) 771-6314
rkenna@redhat.com
prev parent reply other threads:[~2005-10-05 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 8:54 [linux-lvm] LVM multipathing? Pavel A Tsvetkov
2005-10-05 13:14 ` Rob Kenna [this message]
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=4343D1B4.800@redhat.com \
--to=rkenna@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).