From: Lars Marowsky-Bree <lmb@suse.de>
To: Anu Matthew <anu.matthew@bms.com>, linux-raid@vger.kernel.org
Subject: Re: monitoring multipath arrays plus inconsistent /proc/mdstat?
Date: Fri, 22 Oct 2004 23:25:31 +0200 [thread overview]
Message-ID: <20041022212531.GE7205@marowsky-bree.de> (raw)
In-Reply-To: <41797136.2050209@bms.com>
On 2004-10-22T16:44:38, Anu Matthew <anu.matthew@bms.com> wrote:
> May I ask, why? We are to evaluate Power Path also for 2.4, and am just
> curious why it is not going to run on 2.6? That could be a very important
> factor in decision making if it won't make it on 2.6.x
Because EMC is very forthcoming about supporting the proper way of doing
multipathing on Linux in 2.6 (based on the Open Source Device-Mapper
multipath functionality + the multipath-tools package) and actively
supporting me developing that feature by providing technical specs and
hardware, I don't really see a need for using Power Path any longer on
2.6 platforms.
I could understand that they may want to provide it for legacy
installations who want to slowly transition though, but they've not
mentioned it yet; personally I'd think it would be kind of pointless
;-)
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX AG - A Novell company
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2004-10-22 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 16:16 monitoring multipath arrays plus inconsistent /proc/mdstat? Anu Matthew
2004-10-21 16:51 ` Lars Marowsky-Bree
2004-10-22 5:41 ` Lajber Zoltan
2004-10-22 9:17 ` Lars Marowsky-Bree
2004-10-22 20:44 ` Anu Matthew
2004-10-22 21:25 ` Lars Marowsky-Bree [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=20041022212531.GE7205@marowsky-bree.de \
--to=lmb@suse.de \
--cc=anu.matthew@bms.com \
--cc=linux-raid@vger.kernel.org \
/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).