From: Anu Matthew <anu.matthew@bms.com>
To: linux-raid@vger.kernel.org
Subject: Re: multipath md devices
Date: Wed, 22 Sep 2004 18:20:54 -0400 [thread overview]
Message-ID: <4151FAC6.8090204@bms.com> (raw)
In-Reply-To: <1095888922.4196.1548.camel@compaq.xsintricity.com>
//
Yeah, IBM wrote a little app to help with that. We stuffed it into the
mdadm package we ship since that seemed the most appropriate place for
it. It's called mdmpd and that's it's job basically. Very simple app,
but doesn't run on upstream kernels at the moment (it wants the md event
interface which hasn't yet been submitted upstream by Neil).
//
Doug, thanks a lot, we appreciate your response.
One of our boxes with the multipath problem (sic) runs on RHEL ES3.0
with active RHN subscription and is at 2.4.21-15.ELsmp, and has
mdadm-1.5.0-3, with mdmpd running. Yet it crashed last week as the paths
went away from a SAN switch f/w upgrade, as they took off the paths one
4 hours after another, but never both the paths at the same time.
I saw your post on Bugzilla, dated 2004-06-07 about the md Event
Interface Patch. Do we still have to throw that patch in, manually? Or
does 2.4.21-20.ELsmp have it already? I tried to read up the Change Log
and File lists, could gather nothing much.
Thanks,
--Anu Matthew
next prev parent reply other threads:[~2004-09-22 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 20:41 multipath md devices Anu Matthew
2004-09-22 21:35 ` Doug Ledford
2004-09-22 22:20 ` Anu Matthew [this message]
2004-09-23 5:46 ` Luca Berra
2004-09-24 1:10 ` Neil Brown
2004-09-24 16:41 ` Doug Ledford
-- strict thread matches above, loose matches on Subject: below --
2004-09-22 21:55 Doug Griswold
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=4151FAC6.8090204@bms.com \
--to=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).