From: Lars Marowsky-Bree <lmb@suse.de>
To: Brian Beattie <alchemy@us.ibm.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Mario Mikocevic <mozgy@hinet.hr>,
linux-kernel@vger.kernel.org
Subject: Re: FC & MULTIPATH !? (any hope?)
Date: Mon, 14 Jan 2002 21:11:48 +0100 [thread overview]
Message-ID: <20020114211148.B935@marowsky-bree.de> (raw)
In-Reply-To: <200201141524.g0EFOqj09542@localhost.localdomain> <1011037987.918.0.camel@w-beattie1>
In-Reply-To: <1011037987.918.0.camel@w-beattie1>
On 2002-01-14T11:53:07,
Brian Beattie <alchemy@us.ibm.com> said:
> I've been working with the multipath code. Trying to add functionality
> to it. While I have not yet looked at this particular issue, if there
> is interest I would be willing to see what can be done. I do not think
> it would be a big deal to add the functionality to reactivate a dead
> path. It should not be too hard to attempt to do so automatically.
It should only be tried on demand, or at least possible to configure it in
this way; more safe.
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-14 20:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 15:24 FC & MULTIPATH !? (any hope?) 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2002-01-18 7:07 ` Lars Marowsky-Bree
2002-01-18 22:30 ` Brian Beattie
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=20020114211148.B935@marowsky-bree.de \
--to=lmb@suse.de \
--cc=James.Bottomley@SteelEye.com \
--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.