From: "Doug Griswold" <griswld@cio.sc.gov>
To: lmb@suse.de
Cc: linux-raid@vger.kernel.org
Subject: Re: md multipath and failover
Date: Thu, 11 Sep 2003 13:30:41 -0400 [thread overview]
Message-ID: <sf607904.085@gw.state.sc.us> (raw)
Here is a update on my situation. I downloaded the md-mp patch and
tried to apply it to the Red Hat kernel source 2.4.9-27enterprise
kernel, this did not patch correctly. I then downloaded the 2.4.22
kernel and applied with success. The box now fails over in a matter of
seconds instead of minutes it still doesn't failback but that's no big
deal. My next question is how can I apply this patch to the red hat
supplied kernel 2.4.9-27 enterprise so I will still have red hat support
on this kernel? Also is there away with this patch applied to get
failback?
Thanks,
Doug
>>> Lars Marowsky-Bree <lmb@suse.de> 09/11/03 03:43AM >>>
On 2003-09-10T18:55:41,
Doug Griswold <griswld@cio.sc.gov> said:
> Alright I got md/multipath to failover with 2 emulex hba's on red
hat
> advanced server 2.1 kernel version 2.4.9-27enterprise. My next new
> problem is that it took five minutes to fail over from when I yanked
one
> of the fibre channel cables. Where could this timeout come from?
I
> have tried several times but each time it takes 5 minutes to
failover.
> Also it won't failback. Any ideas out there.
The plain md multipath can't do failback automatically. People's
opinion
on whether that is a good idea do differ ;-)
The timeout is the time needed until the damn (sorry) Linux Kernel
SCSI
layers give up retrying and then pass the error code up to md for
handling. You can maybe try tuning some emulex parameters to fix that.
If you want load balancing for the md multipath, you could try
checking
out my patch at ftp://ftp.suse.com/pub/people/lmb/md-mp/ vs 2.4, it
adds
some features to md and also makes it quite a bit more robust.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering ever tried. ever failed. no
matter.
SuSE Labs try again. fail again. fail
better.
Research & Development, SuSE Linux AG -- Samuel Beckett
-
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
-
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
next reply other threads:[~2003-09-11 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 17:30 Doug Griswold [this message]
2003-09-18 9:12 ` md multipath and failover Lars Marowsky-Bree
-- strict thread matches above, loose matches on Subject: below --
2003-09-11 11:07 Doug Griswold
2003-09-10 22:55 Doug Griswold
2003-09-11 7:43 ` Lars Marowsky-Bree
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=sf607904.085@gw.state.sc.us \
--to=griswld@cio.sc.gov \
--cc=linux-raid@vger.kernel.org \
--cc=lmb@suse.de \
/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).