All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tore Anderson <tore@linpro.no>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: multibus / failover and EMC CX600
Date: Wed, 17 Oct 2007 12:40:36 +0200	[thread overview]
Message-ID: <4715E6A4.7060308@linpro.no> (raw)
In-Reply-To: <061401c810a7$cac685d0$0a00a8c0@ALDI2>

* Gerald Nowitzky

> What I'd like to have is multibus via HBA-A -> SW-A -> SP-A  and
> HBA-B -> SW-B -> SP-A to the active SP and, in case both paths to the
> active SP fail, a trespas of my LUN to SP-B, multibus to the other
> SP-B and vice versa.

Try the following:

  prio_callout "/sbin/mpath_prio_emc /dev/%n"
  path_grouping_policy group_by_prio

The -EEXIST message is a kernel bug, see the thread starting at
<http://lkml.org/lkml/2007/8/14/106> for more information.  It might be
possible to work around it by disabling async SCSI scanning, if not
there's a patch from Matthew Wilcox that removed most of those -EEXIST
errors (but not all the corner cases).

It kinda sucks that the kernel removes the SCSI devices pointing to
blocked rports.  Wonder if it's possible to disable that somehow...

Regards
-- 
Tore Anderson

  reply	other threads:[~2007-10-17 10:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17 10:23 multibus / failover and EMC CX600 Gerald Nowitzky
2007-10-17 10:40 ` Tore Anderson [this message]
2007-10-17 11:08   ` Hannes Reinecke
2007-10-17 12:32     ` Tore Anderson
2007-10-17 14:48       ` Gerald Nowitzky
2007-10-17 16:01         ` Tore Anderson
2007-10-17 18:04           ` Gerald Nowitzky
2007-10-18  6:19             ` Hannes Reinecke
2007-10-18  6:55               ` Gerald Nowitzky
2007-10-18  7:12                 ` Hannes Reinecke
2007-10-18  8:07                   ` Gerald Nowitzky
2007-10-19 22:35                     ` David Strand
2007-10-17 19:38           ` Gerald Nowitzky
2007-10-18  6:01             ` Tore Anderson
2007-10-18  6:19               ` Tore Anderson
2007-10-17 19:49       ` Mike Christie

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=4715E6A4.7060308@linpro.no \
    --to=tore@linpro.no \
    --cc=dm-devel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.