From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Benjamin Marzinski <bmarzins@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] libmultipath: update 3PARdata builtin config
Date: Thu, 13 Jul 2017 20:25:30 +0200 [thread overview]
Message-ID: <e1f2c3d3-77d1-bb86-c212-b65719815065@gmail.com> (raw)
In-Reply-To: <20170629145731.GR2940@octiron.msp.redhat.com>
On 06/29/2017 04:57 PM, Benjamin Marzinski wrote:
>>> + .fast_io_fail = 10,
>>> + .dev_loss = MAX_DEV_LOSS_TMO,
> On Wed, Jun 28, 2017 at 07:48:38PM +0200, Xose Vazquez Perez wrote:
>
>> 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.
Those arguments should come from the vendor.
"dev_loss_tmo 14" is recommended(???) in latest 3PAR docs (Jun 2017):
- HPE 3PAR SUSE Linux Enterprise Implementation Guide (Wed 14 Jun 2017 11:48:14 PM CEST)
http://h20564.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay/?docId=c02663748
- HPE 3PAR Red Hat Enterprise Linux and Oracle Linux Implementation Guide (Wed 14 Jun 2017 12:10:06 AM CEST)
http://h20564.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay/?docId=c04448818
next prev parent reply other threads:[~2017-07-13 18:25 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
2017-07-13 18:25 ` Xose Vazquez Perez [this message]
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=e1f2c3d3-77d1-bb86-c212-b65719815065@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=bmarzins@redhat.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