From: Neil Brown <neilb@suse.de>
To: Billy Crook <bcrook@advancedclustering.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Multipath behavior
Date: Thu, 8 May 2008 15:12:40 +1000 [thread overview]
Message-ID: <18466.35784.682339.288410@notabene.brown> (raw)
In-Reply-To: message from Billy Crook on Tuesday April 22
On Tuesday April 22, bcrook@advancedclustering.com wrote:
> I am considering implementing multipath for iSCSI. Documentation is
> scant though, so I thought I'd ask my questions here.
>
> Does mdadm multipath loadbalance IO, or just allow for failover, or both?
> Is there any advantage to notifying mdadm pre-emptively if possible
> before a path goes down?
> I assume bringing a path online has to be done manually like adding a
> disk. Can spare paths be used?
>
> The kernel involved is 2.6.18-53.1.14.el5.
>
> Thank you for your time.
I recommend against using md based multipath. It is not being
seriously maintained.
dm (aka device mapper) based multipath is where the action is.
NeilBrown
prev parent reply other threads:[~2008-05-08 5:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 17:48 Multipath behavior Billy Crook
2008-05-08 5:12 ` Neil Brown [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=18466.35784.682339.288410@notabene.brown \
--to=neilb@suse.de \
--cc=bcrook@advancedclustering.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