public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: Bernd Eckenfels <ecki@calista.eckenfels.6bone.ka-ip.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Accessing the same disk via multiple channels
Date: Fri, 14 Feb 2003 11:03:16 +0100	[thread overview]
Message-ID: <20030214100316.GA3422@marowsky-bree.de> (raw)
In-Reply-To: <E18jS75-0007na-00@calista.inka.de>

On 2003-02-13T23:45:51,
   Bernd Eckenfels <ecki@calista.eckenfels.6bone.ka-ip.net> said:

> You can use the multipath option to md which can do that.
> 
> Basically there are two options, a failover and a load balancing option. The
> problem with failover is, to detect the actual failure reliable, toe problem
> with load balancing is, that not all san configurations allow this.
> 
> http://www-124.ibm.com/storageio/multipath/md-multipath/index.php
> 
> this is at least in 2.4.20-xfs

That one? Ouch, it is a bit dated according to the webpage ;-) I don't recall
that it was discussed on LKML, either.

SuSE (Jens Axboe and myself) have also done work on the md multipathing,
supporting failover and load balancing and in general giving the code a rinse;
as well as extensions to mdadm to make them work.

The patches currently live at http://lars.marowsky-bree.de/dl/md-mp/

(And are included in SuSE's kernel release, of course ;-)

Currently, for 2.5 / 2.6, I think I really like the SCSI midlayer stuff. In
the past, I didn't, because it constrains everything to SCSI. But then,
everything so far _has_ been SCSI, except for weird arch stuff like s390(x)
DASDs ;-)

Doing it in the SCSI layer has the advantage of not being constrained to block
devices, but also working with tapes. Oh well, we'll see ;-)


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
Principal Squirrel 
SuSE Labs - Research & Development, SuSE Linux AG
  
"If anything can go wrong, it will." "Chance favors the prepared (mind)."
  -- Capt. Edward A. Murphy            -- Louis Pasteur

  reply	other threads:[~2003-02-14  9:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13 19:49 Accessing the same disk via multiple channels Jurjen Oskam
2003-02-13 22:45 ` Bernd Eckenfels
2003-02-14 10:03   ` Lars Marowsky-Bree [this message]
2003-02-14 22:01     ` Tim Pepper
2003-02-14 23:37       ` Patrick Mansfield
2003-02-17  9:52         ` Lars Marowsky-Bree
  -- strict thread matches above, loose matches on Subject: below --
2003-02-14  3:20 steve cameron
2003-02-14 16:27 ` Lars Marowsky-Bree
2003-02-14 18:17   ` Patrick Mansfield

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=20030214100316.GA3422@marowsky-bree.de \
    --to=lmb@suse.de \
    --cc=ecki@calista.eckenfels.6bone.ka-ip.net \
    --cc=linux-kernel@vger.kernel.org \
    /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