public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jurjen Oskam <jurjen@quadpro.stupendous.org>
To: linux-kernel@vger.kernel.org
Subject: Accessing the same disk via multiple channels
Date: Thu, 13 Feb 2003 20:49:17 +0100	[thread overview]
Message-ID: <20030213194917.GA8479@quadpro.stupendous.org> (raw)

Hi everybody,

here's something I've been wondering about. On my work, we have
an EMC2 Symmetrix in a SAN environment, with (until now) only
AIX boxes attached to the SAN.

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.

EMC2 provide a piece of software called PowerPath, which takes advantage of
this situation. It provides yet another device (let's say /dev/powersda), which
uses the (identical) native devices /dev/sda and /dev/sdc. If one of those
two would disappear, access to powersda would still be possible.

How does linux as it is now handle the situation of one physical device
presented via multiple paths (without extra software)?

-- 
Jurjen Oskam

PGP Key available at http://www.stupendous.org/

             reply	other threads:[~2003-02-13 19:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13 19:49 Jurjen Oskam [this message]
2003-02-13 22:45 ` Accessing the same disk via multiple channels Bernd Eckenfels
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
  -- 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=20030213194917.GA8479@quadpro.stupendous.org \
    --to=jurjen@quadpro.stupendous.org \
    --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