All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Zeimetz <bernd@bzed.de>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Multipath and SAN Fabric failover
Date: Thu, 07 Sep 2006 20:09:38 +0200	[thread overview]
Message-ID: <45006062.6020800@bzed.de> (raw)
In-Reply-To: <20060907133943.4aa92481@localhost>

Heya,

I think you should just try an empty multipath.conf, only put the 
blacklist in. The EMC CX needs pp_emc as prio callout for example. The 
defaults within multipath should just work.
Also make sure your failovermode and arraycommpath are both set to 1. A 
few hints are mentioned on 
http://christophe.varoqui.free.fr/wiki/wakka.php?wiki=TestedEnvironments
Please fill in if you find something that's missing there.

Best regards,

Bernd Zeimetz


John Little wrote:
> Hi all,
>
> I am trying to setup our server so that we have fabric failover from
> the san.  However my file sytem comes up read-only when I pull a cable
> for testing.
>
> I am using the following:
> SLES 10
> multipath-tools-0.4.6-25.8
> q-logic 2342 dual port hba
> emc cx600 san
> (4) McData DS-24 switches (2 for fabric a and 2 for fabric b)
>
>
>
> /etc/multipath.conf has the following entries:
>
> xen2:~ # grep -v "#" /etc/multipath.conf
> defaults {
>         udev_dir                /dev
>         polling_interval        10
>         selector                "round-robin 0"
>         getuid_callout          "/sbin/scsi_id -g -u -s /block/%n"
>         prio_callout            /bin/true
>         failback                immediate
> }
> devnode_blacklist {
>         device {
>                 vendor SEAGATE
>                 product ST973401LSUN72G
>         }
> }
> multipaths {
>         multipath {
>                 wwid                    360060160f06109004352b218eb51da11
>                 alias                   capsprod
>                 path_grouping_policy    failover
>                 path_checker            readsector0
>                 path_selector           "round-robin 0"
>                 failback                immediate
>         }
> }
>
> Can someone point me in the right direction to get this resolved?
>
> Best regards,
> John Little, Network Systems
> Hendricks Regional Health
> http://hendrickshospital.org
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
>   

  reply	other threads:[~2006-09-07 18:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 17:39 Multipath and SAN Fabric failover John Little
2006-09-07 18:09 ` Bernd Zeimetz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-08 15:32 John Little

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=45006062.6020800@bzed.de \
    --to=bernd@bzed.de \
    --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.