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: Thu, 28 Feb 2019 13:53:30 -0600 [thread overview]
Message-ID: <20190228195330.GQ3023@octiron.msp.redhat.com> (raw)
In-Reply-To: <d915601a3472d7448e57f968e2ec3a63c627a35e.camel@cgi.com>
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
> for f in /sys/class/fc_remote_ports/rport-*/dev_loss_tmo; do
> d=$(dirname $f); echo $(basename $d):$(cat $d/node_name):$(cat $f);
> done
>
> rport-3:0-0:0x5742b0f00007c500:10
> rport-3:0-1:0x5742b0f00007c500:10
> rport-3:0-2:0x5742b0f00007c500:10
> rport-3:0-3:0x5000097408369800:30
> rport-3:0-4:0x500009757804cbff:30
> rport-4:0-0:0x5742b0f00007c500:10
> rport-4:0-1:0x5742b0f00007c500:10
> rport-4:0-2:0x5000097408369800:30
> rport-4:0-3:0x5742b0f00007c500:10
> rport-4:0-4:0x500009757804cbff:30
> rport-5:0-0:0x5742b0f00007c500:10
> rport-5:0-1:0x5742b0f00007c500:10
> rport-5:0-2:0x5742b0f00007c500:10
> rport-5:0-3:0x5000097408369800:30
> rport-5:0-4:0x500009757804cbff:30
> rport-6:0-0:0x5742b0f00007c500:10
> rport-6:0-1:0x5742b0f00007c500:10
> rport-6:0-2:0x5000097408369800:30
> rport-6:0-3:0x5742b0f00007c500:10
> rport-6:0-4:0x500009757804cbff:30
>
> systool is giving me the same information:
>
> systool -c fc_remote_ports -v | grep dev_loss_tmo
>
> dev_loss_tmo = "10"
> dev_loss_tmo = "10"
> dev_loss_tmo = "10"
> dev_loss_tmo = "10"
> dev_loss_tmo = "10"
> dev_loss_tmo = "10"
> dev_loss_tmo = "10"
> dev_loss_tmo = "10"
> dev_loss_tmo = "10"
> dev_loss_tmo = "30"
> dev_loss_tmo = "10"
> dev_loss_tmo = "30"
> dev_loss_tmo = "30"
> dev_loss_tmo = "10"
> dev_loss_tmo = "30"
> dev_loss_tmo = "10"
> dev_loss_tmo = "30"
> dev_loss_tmo = "30"
> dev_loss_tmo = "30"
> dev_loss_tmo = "30"
>
> Where is this value coming from? May this be a bug? I couldn't find
> anything useful on the Internet regarding this.
>
> I am using the following versions:
>
> rpm -qa multipath-tools
> multipath-tools-0.4.9-109.1
>
> uname -a
> Linux mysystem 3.0.101-63-default #1 SMP Tue Jun 23 16:02:31 UTC 2015
> (4b89d0c) x86_64 x86_64 x86_64 GNU/Linux
>
> Thanks for your help!
>
> Kind regards,
>
> Bruno
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2019-02-28 19:53 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 [this message]
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
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=20190228195330.GQ3023@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