From: "Benjamin Marzinski" <bmarzins@redhat.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] libmultipath: update 3PARdata builtin config
Date: Thu, 29 Jun 2017 09:57:31 -0500 [thread overview]
Message-ID: <20170629145731.GR2940@octiron.msp.redhat.com> (raw)
In-Reply-To: <5d7143cd-4964-93ca-1e71-0119eb2a8ea1@gmail.com>
On Wed, Jun 28, 2017 at 07:48:38PM +0200, Xose Vazquez Perez wrote:
> On 06/26/2017 09:03 PM, Benjamin Marzinski wrote:
>
> > This updated config comes from hp.
>
> It would be nice to have more information.
> Why and when is this needed?
I assume the change to dev_loss_tmo is simply a preference issue. Like
Netapp, they don't want their devices to get auto-removed when they go
down. I also assume that in their internal testing, they hit cases where
5 seconds wasn't enough time to wait for some transient issue with the
array to resolve. At any rate, I'm simply passing along their request,
which seems like a perfectly reasonable one to me.
-Ben
>
>
> BTW: HPE 'MSA 205x' and 'StoreVirtual 3200'(LeftHand) are missing.
>
> > Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
> > ---
> > libmultipath/hwtable.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/libmultipath/hwtable.c b/libmultipath/hwtable.c
> > index 390d143..54bdcfc 100644
> > --- a/libmultipath/hwtable.c
> > +++ b/libmultipath/hwtable.c
> > @@ -49,6 +49,8 @@ static struct hwentry default_hw[] = {
> > .hwhandler = "1 alua",
> > .prio_name = PRIO_ALUA,
> > .no_path_retry = 18,
> > + .fast_io_fail = 10,
> > + .dev_loss = MAX_DEV_LOSS_TMO,
> > },
> > {
> > /* RA8000 / ESA12000 */
> >
next prev parent reply other threads:[~2017-06-29 14:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 19:03 [PATCH] libmultipath: update 3PARdata builtin config Benjamin Marzinski
2017-06-28 17:48 ` Xose Vazquez Perez
2017-06-29 14:57 ` Benjamin Marzinski [this message]
2017-07-13 18:25 ` Xose Vazquez Perez
2017-07-28 22:37 ` Benjamin Marzinski
2017-07-31 11:37 ` Xose Vazquez Perez
2017-08-05 6:36 ` Christophe Varoqui
-- strict thread matches above, loose matches on Subject: below --
2017-08-05 11:23 Xose Vazquez Perez
2017-08-05 11:54 ` Christophe Varoqui
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=20170629145731.GR2940@octiron.msp.redhat.com \
--to=bmarzins@redhat.com \
--cc=dm-devel@redhat.com \
--cc=xose.vazquez@gmail.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