Linux Device Mapper development
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Christophe Varoqui <christophe.varoqui@gmail.com>
Subject: Re: [PATCH] multipath: update netapp config
Date: Thu, 10 Jan 2013 19:07:31 +0100	[thread overview]
Message-ID: <50EF0363.5090404@gmail.com> (raw)
In-Reply-To: <20130108054443.GZ19059@ether.msp.redhat.com>

On 01/08/2013 06:44 AM, Benjamin Marzinski wrote:
> The netapp config now used the retain_attached_hwhandler and
> detect_prio options to automatically configure correctly for both ALUA and
> non-ALUA setups. NetApp also requested that dev_loss_tmo be set to
> the maximum for netapp devices.
> 
> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
> ---
>  libmultipath/hwtable.c |    3 +++
>  1 file changed, 3 insertions(+)
> 
> Index: multipath-tools-120821/libmultipath/hwtable.c
> ===================================================================
> --- multipath-tools-120821.orig/libmultipath/hwtable.c
> +++ multipath-tools-120821/libmultipath/hwtable.c
> @@ -871,9 +871,12 @@ static struct hwentry default_hw[] = {
>  		.rr_weight     = RR_WEIGHT_NONE,
>  		.no_path_retry = NO_PATH_RETRY_UNDEF,
>  		.minio         = 128,
> +		.dev_loss      = MAX_DEV_LOSS_TMO,
>  		.checker_name  = TUR,
>  		.prio_name     = PRIO_ONTAP,
>  		.prio_args     = NULL,
> +		.retain_hwhandler = RETAIN_HWHANDLER_ON,
> +		.detect_prio   = DETECT_PRIO_ON,
>  	},
>  	/*
>  	 * NEXENTA/COMSTAR controller family
> 

ditto.

      reply	other threads:[~2013-01-10 18:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08  5:44 [PATCH] multipath: update netapp config Benjamin Marzinski
2013-01-10 18:07 ` Xose Vazquez Perez [this message]

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=50EF0363.5090404@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=christophe.varoqui@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox