From: Lars Marowsky-Bree <lmb@suse.de>
To: Brian Beattie <alchemy@us.ibm.com>
Cc: Mario Mikocevic <mozgy@hinet.hr>, linux-kernel@vger.kernel.org
Subject: Re: FC & MULTIPATH !? (any hope?)
Date: Fri, 18 Jan 2002 08:07:14 +0100 [thread overview]
Message-ID: <20020118080714.I937@marowsky-bree.de> (raw)
In-Reply-To: <20020114123301.B30997@danielle.hinet.hr> <1011310615.519.3.camel@w-beattie1>
In-Reply-To: <1011310615.519.3.camel@w-beattie1>
On 2002-01-17T15:36:54,
Brian Beattie <alchemy@us.ibm.com> said:
> 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.
Combined with the enhancements this makes a lot of sense.
The enhancements are very much required, especially the way to mark a path as
good again manually.
I would also liks easily parseable /proc file to query the status of a
multi-path device, including all paths associated with it.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
Perfection is our goal, excellence will be tolerated. -- J. Yahl
next prev parent reply other threads:[~2002-01-18 7:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 11:33 FC & MULTIPATH !? (any hope?) Mario Mikocevic
2002-01-14 12:07 ` Lars Marowsky-Bree
2002-01-14 16:21 ` Peter Rival
2002-01-17 23:36 ` Brian Beattie
2002-01-18 7:07 ` Lars Marowsky-Bree [this message]
2002-01-18 22:30 ` Brian Beattie
-- strict thread matches above, loose matches on Subject: below --
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=20020118080714.I937@marowsky-bree.de \
--to=lmb@suse.de \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.