From: Benjamin Marzinski <bmarzins@redhat.com>
To: "Martins, Bruno O" <bruno.martins@cgi.com>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: Re: multipathd ignoring dev_loss_tmo setting
Date: Tue, 12 Mar 2019 17:32:16 -0500 [thread overview]
Message-ID: <20190312223216.GC13295@octiron.msp.redhat.com> (raw)
In-Reply-To: <1379896535dccc69dc07bf16a8be7696392261a3.camel@cgi.com>
On Mon, Mar 04, 2019 at 09:48:59AM +0000, Martins, Bruno O wrote:
> On Fri, 2019-03-01 at 11:35 -0600, Benjamin Marzinski wrote:
> > On Fri, Mar 01, 2019 at 10:04:52AM +0000, Martins, Bruno O wrote:
> > > On Thu, 2019-02-28 at 13:53 -0600, Benjamin Marzinski wrote:
> > > > On Thu, Feb 28, 2019 at 11:38:22AM +0000, Martins, Bruno O wrote:
> > > > > Hello guys,
> > > > >
> > > > > I am trying to modify /etc/multipath.conf on my system so that
> > > > > the
> > > > > parameter 'dev_loss_tmo' is changed from the default value.
> > > > >
> > > > > However, when checking the value currently in use I am getting
> > > > > the
> > > > > wrong value (which is '30') for some of the remote ports:
> > > > >
> > > >
> > > > Are you sure those rports are used by multipath devices?
> > > > multipath
> > > > only
> > > > changes dev_loss_tmo for rports associated with a multipath path
> > > > device.
> > > >
> > > > -Ben
> > > >
>
> Hello Ben,
>
> Then I believe this rport's with wrong dev_loss_tmo are part of
> multipathd. Is this correct?
yeah, that looks correct. If you run
# multipath -r
does that correct the issue? If not, can you attach the result of
running
# multipath -rv 3
-Ben
>
> Best regards,
>
> Bruno
next prev parent reply other threads:[~2019-03-12 22:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 11:38 multipathd ignoring dev_loss_tmo setting Martins, Bruno O
2019-02-28 12:08 ` Steffen Maier
2019-02-28 19:53 ` Benjamin Marzinski
2019-03-01 10:04 ` Martins, Bruno O
2019-03-01 17:35 ` Benjamin Marzinski
2019-03-04 9:48 ` Martins, Bruno O
2019-03-12 22:32 ` Benjamin Marzinski [this message]
2019-03-04 12:09 ` Martin Wilck
2019-03-04 14:09 ` Martins, Bruno O
2019-03-04 14:40 ` Martin Wilck
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=20190312223216.GC13295@octiron.msp.redhat.com \
--to=bmarzins@redhat.com \
--cc=bruno.martins@cgi.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