From: "Philip R. Auld" <pauld@egenera.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Simon Kelley <simon@thekelleys.org.uk>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Is there a grand plan for FC failover?
Date: Wed, 28 Jan 2004 10:02:36 -0500 [thread overview]
Message-ID: <20040128100236.D11527@vienna.EGENERA.COM> (raw)
In-Reply-To: <1075131446.2290.29.camel@mulgrave>; from James.Bottomley@steeleye.com on Mon, Jan 26, 2004 at 09:37:25AM -0600
Hi,
Rumor has it that on Mon, Jan 26, 2004 at 09:37:25AM -0600 James Bottomley said:
> On Mon, 2004-01-26 at 08:18, Simon Kelley wrote:
>
> > I'm very much in favour of using drivers which are developed in the
> > kernel mainline but I have an application which needs failover so I
> > might be forced back to the qlogic-distributed code.
>
> Yes, the direction coming out of KS/OLS last year was to use the dm or
> md multi-path code to sit the failover driver on top of sd (or any other
> block driver).
>
> The idea being that the Volume Manager layer is the most stack generic
> place to do this type of thing. The thread on this is here:
>
> http://marc.theaimsgroup.com/?t=106005575400003
>
There are some issues left un-resolved with this approach.
The one's that come mind are:
1) load balancing when possible: it's not enough to be just a
failover mechanism.
2) requiring a userspace program to execute for failover is
problematic when it could be the root disk that needs
failing over.
3) Handling partitions is a problem.
I see multipath and md/RAID as two different animals. Multipathing is
multiple ways to reach the same physical block. That is it's under
the logical layer. While RAID is multiple ways to reach the same
logical block. It's basically many-to-one vs one-to-many. Having
multiple physical paths to a logical partition is a little
counter-intuitive.
That said, I'm all for getting Linux to have a decent multipath
implementation, at what ever layer is agreed upon. I'd love to
be able to use the native Linux multipathing and stop supporting
the ones I've written.
FWIW,
Phil
> James
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Philip R. Auld, Ph.D. Egenera, Inc.
Principal Software Engineer 165 Forest St.
(508) 858-2628 Marlboro, MA 01752
next prev parent reply other threads:[~2004-01-28 15:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 14:18 Is there a grand plan for FC failover? Simon Kelley
2004-01-26 15:37 ` James Bottomley
2004-01-28 15:02 ` Philip R. Auld [this message]
2004-01-28 16:57 ` James Bottomley
2004-01-28 18:00 ` Philip R. Auld
2004-01-28 20:47 ` Patrick Mansfield
2004-01-28 22:14 ` James Bottomley
2004-01-29 0:55 ` Patrick Mansfield
2004-01-30 19:48 ` [dm-devel] " Joe Thornber
2004-01-31 9:30 ` Jens Axboe
2004-01-31 16:59 ` Philip R. Auld
2004-01-31 17:42 ` Jens Axboe
2004-02-12 15:17 ` Philip R. Auld
2004-02-12 15:28 ` Arjan van de Ven
2004-02-12 16:03 ` Philip R. Auld
2004-01-28 22:37 ` Mike Christie
2004-01-29 15:24 ` Philip R. Auld
2004-01-29 16:00 ` James Bottomley
2004-01-29 23:25 ` Mike Christie
-- strict thread matches above, loose matches on Subject: below --
2004-01-28 21:02 Smart, James
2004-01-28 22:16 ` James Bottomley
2004-01-29 14:49 ` Philip R. Auld
2004-01-29 15:05 ` James Bottomley
2004-01-29 17:35 Smart, James
2004-01-29 18:31 ` Mike Anderson
2004-01-29 18:31 ` James Bottomley
2004-01-29 18:41 Smart, James
2004-01-29 19:37 Smart, James
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=20040128100236.D11527@vienna.EGENERA.COM \
--to=pauld@egenera.com \
--cc=James.Bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=simon@thekelleys.org.uk \
/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