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: Re: Round Robin vs Active/Passive
Date: Thu, 05 Jun 2008 08:54:55 +0200	[thread overview]
Message-ID: <48478DBF.3060709@linpro.no> (raw)
In-Reply-To: <01d601c8bd1a$c5fd99b0$0201a8c0@zeug>

* Sebastian Herbszt

> The comment and code from libmultipath/prioritizers/emc.c
> 
>  if ( /* Effective initiator type */
>       sense_buffer[27] != 0x03
>   /*
>    * Failover mode should be set to 1 (PNR failover mode)
>    * or 4 (ALUA failover mode).
>    */
>   || (((sense_buffer[28] & 0x07) != 0x04) &&
>       ((sense_buffer[28] & 0x07) != 0x06))
>   /* Arraycommpath should be set to 1 */
>   || (sense_buffer[30] & 0x04) != 0x04) {
>   pp_emc_log(0, "path not correctly configured for failover");
>  }
> 
> doesn't help with the detection part?

Not really, there's no way I can put this into a device{} section to
differentiate between two CLARiiONs running different failover modes.

What I need to do is this:

# My new CX3-40f which supports ALUA (preferred) as well as PNR
device {
	vendor DGC
	product *
	product_blacklist LUNZ
	alua_capable yes
	[..ALUA optimised settings...]
}

# My old CX200, only supports PNR
device {
	vendor DGC
	product *
	product_blacklist LUNZ
	alua_capable no
	[..PNR optimised settings...]
}

...but there's no such thing as the "alua_capable" setting or any other
setting that can be used to distinguish between the two CLARiiONs, as
far as I know, so I have to use both arrays in PNR mode even though the
newest one of them supports ALUA.

Please prove me wrong...  ;-)

Regards,
-- 
Tore Anderson

  reply	other threads:[~2008-06-05  6:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8a6b34b03e0524aa66c862534fee9b7a@www3.mail.volny.cz>
2008-05-21 11:41 ` INFO: task md2_resync:7950 blocked for more than 120 seconds Neil Brown
2008-05-21 14:48   ` Round Robin vs Active/Passive Craig Simpson
2008-05-21 15:32     ` Craig Simpson
2008-05-21 18:23       ` Tore Anderson
2008-05-21 20:21         ` Craig Simpson
2008-05-21 21:01           ` Tore Anderson
2008-05-21 21:49             ` Craig Simpson
2008-05-21 23:41               ` Craig Simpson
2008-05-22 12:00                 ` Tore Anderson
2008-05-22  8:24         ` Domenico Viggiani
2008-05-22 11:57           ` Tore Anderson
2008-05-23  7:16           ` Hannes Reinecke
2008-05-23  8:00             ` Tore Anderson
2008-05-23  8:55               ` Hannes Reinecke
2008-05-23  9:42                 ` Tore Anderson
2008-05-23 10:36               ` Domenico Viggiani
2008-05-23 10:46                 ` Tore Anderson
2008-05-23 21:16                   ` Sebastian Herbszt
2008-06-05  6:54                     ` Tore Anderson [this message]
2008-06-05  7:20                       ` Hannes Reinecke
2008-06-06  7:19                         ` Tore Anderson

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=48478DBF.3060709@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.