From: Patrick Mansfield <patmans@us.ibm.com>
To: mauelshagen@sistina.com
Cc: christophe.varoqui@free.fr, linux-scsi@vger.kernel.org
Subject: Re: [lvm] [christophe.varoqui@free.fr: dm multipath target]
Date: Fri, 22 Aug 2003 07:59:53 -0700 [thread overview]
Message-ID: <20030822075953.A28851@beaverton.ibm.com> (raw)
In-Reply-To: <20030822105146.B8420@sistina.com>; from Heinz.Mauelshagen@t-online.de on Fri, Aug 22, 2003 at 10:51:46AM +0200
On Fri, Aug 22, 2003 at 10:51:46AM +0200, Heinz J . Mauelshagen wrote:
> On Thu, Aug 21, 2003 at 06:34:52PM +0200, christophe.varoqui@free.fr wrote:
> > 2) multipath support for "bizarre" arrays need a userspace callback on path failure.
> > Agreement seems to be reached. Still not clear what provides this callback :
> > MD/DM or Block Layer ?
>
> Presumably device-mapper multipath is the one we end up with at the
> end of the day, the answer is DM (the status information retrievable from
> DM provides it already)
The sending of any special command to enable an alternative path (like the
ghost LUN) should be done in a kernel thread or some way that allows the
root file system to be multi-pathed on such devices.
> Setting up a multipath mapping using dmsetup means creating a one line
> mapping table with a couple of parameters per path (see multipath target
> code we plan to release next week).
Is this the same code Joe is working on?
-- Patrick Mansfield
next prev parent reply other threads:[~2003-08-22 15:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030819073926.GA423@fib011235813.fsnet.co.uk>
[not found] ` <20030819094838.F8428@sistina.com>
2003-08-19 9:04 ` [lvm] [christophe.varoqui@free.fr: dm multipath target] christophe.varoqui
2003-08-19 9:51 ` Heinz J . Mauelshagen
2003-08-19 10:48 ` christophe.varoqui
2003-08-19 12:35 ` Heinz J . Mauelshagen
2003-08-19 13:14 ` christophe.varoqui
2003-08-19 13:26 ` christophe.varoqui
2003-08-19 16:23 ` Heinz J . Mauelshagen
2003-08-19 23:22 ` christophe varoqui
2003-08-20 13:02 ` Heinz J . Mauelshagen
2003-08-20 14:19 ` christophe.varoqui
2003-08-21 12:47 ` Heinz J . Mauelshagen
2003-08-21 16:34 ` christophe.varoqui
2003-08-22 8:51 ` Heinz J . Mauelshagen
2003-08-22 14:59 ` Patrick Mansfield [this message]
2003-08-22 15:34 ` christophe.varoqui
2003-08-22 15:55 ` Patrick Mansfield
2003-08-22 16:07 ` christophe.varoqui
2003-08-19 14:19 ` James Bottomley
2003-08-19 16:09 ` Heinz J . Mauelshagen
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=20030822075953.A28851@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=christophe.varoqui@free.fr \
--cc=linux-scsi@vger.kernel.org \
--cc=mauelshagen@sistina.com \
/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