From: Brian Beattie <alchemy@us.ibm.com>
To: Mario Mikocevic <mozgy@hinet.hr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FC & MULTIPATH !? (any hope?)
Date: 17 Jan 2002 15:36:54 -0800 [thread overview]
Message-ID: <1011310615.519.3.camel@w-beattie1> (raw)
In-Reply-To: <20020114123301.B30997@danielle.hinet.hr>
In-Reply-To: <20020114123301.B30997@danielle.hinet.hr>
On Mon, 2002-01-14 at 03:33, Mario Mikocevic wrote:
> Hi,
>
> is there any hope of working combination of MULTIPATH with FC !?
>
> At the moment I am using raid option multipath but it's one way
> street, when one FC connection dies it successfully switches onto
> another FC connection but when that second dies aswell, mount point
> is in a limbo, no switching back to first FC connection.
>
> Any other solutions, patches ?!
>
After analysing the current code in md/multipath and discussing it with
other here who have experience with multipath support I have come up
with the following approach.
When a path fails and there are no more good paths, an attempt will be
made complete the operation using each previously failed path untill the
operation succeds, or all know paths have been tried. If the operation
succeds, that path will be marked good.
When a operation is attempted and no good paths exist, the operation
will be attempted on each know path until success or all know paths are
tried.
Probable enhancements to this would include, provideing a method to mark
a path to not attempt this crude form of auto recovery and a way to mark
a failed path as good. Finally a device wide flag to disable
auto-recovery.
A disadvantage to this approach is that it would potentially, multiply
the amount or time it takes to ultimately fail the attempt, by the
number of paths. This would seem to be acceptable since the alternative
is to fail the operation when a good route might exist.
I would appreciate any thoughts, flames, or suggestions.
next prev parent reply other threads:[~2002-01-17 23:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 11:33 Mario Mikocevic
2002-01-14 12:07 ` Lars Marowsky-Bree
2002-01-14 16:21 ` Peter Rival
2002-01-17 23:36 ` Brian Beattie [this message]
2002-01-18 7:07 ` Lars Marowsky-Bree
2002-01-18 22:30 ` Brian Beattie
2002-01-14 15:24 James Bottomley
2002-01-14 16:11 ` Arjan van de Ven
2002-01-14 19:53 ` Brian Beattie
2002-01-14 20:11 ` 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=1011310615.519.3.camel@w-beattie1 \
--to=alchemy@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mozgy@hinet.hr \
/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
all inboxes | Powered by JetHome®