mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernd Eckenfels <ecki@calista.eckenfels.6bone.ka-ip.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Accessing the same disk via multiple channels
Date: Thu, 13 Feb 2003 23:45:51 +0100	[thread overview]
Message-ID: <E18jS75-0007na-00@calista.inka.de> (raw)
In-Reply-To: <20030213194917.GA8479@quadpro.stupendous.org>

In article <20030213194917.GA8479@quadpro.stupendous.org> you wrote:
> Each server is equipped with 2 FibreChannel cards. The SAN is
> configured to present the same disk (which is in fact a virtual
> Symmetrix device) over two channels. This means the host sees
> two physical devices (as far as that host's concerned) which is
> in fact really only one device. In linux terms: /dev/sda and /dev/sdc
> are exactly the same disks, but the (standard) OS doesn't know this.
...
> How does linux as it is now handle the situation of one physical device
> presented via multiple paths (without extra software)?

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

Greetings
Bernd
-- 
eckes privat - http://www.eckes.org/
Project Freefire - http://www.freefire.org/

  reply	other threads:[~2003-02-13 22:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13 19:49 Jurjen Oskam
2003-02-13 22:45 ` Bernd Eckenfels [this message]
2003-02-14 10:03   ` Lars Marowsky-Bree
2003-02-14 22:01     ` Tim Pepper
2003-02-14 23:37       ` Patrick Mansfield
2003-02-17  9:52         ` Lars Marowsky-Bree
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=E18jS75-0007na-00@calista.inka.de \
    --to=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

all inboxes | Powered by JetHome®