All of lore.kernel.org
 help / color / mirror / Atom feed
From: Muneendra Kumar M <mmandala@Brocade.com>
To: Benjamin Marzinski <bmarzins@redhat.com>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: Re: deterministic io throughput in multipath
Date: Mon, 26 Dec 2016 09:42:48 +0000	[thread overview]
Message-ID: <8cd4cc5f20b540a1b8312ad485711152@BRMWP-EXMB12.corp.brocade.com> (raw)
In-Reply-To: 20161221160940.GG19659@octiron.msp.redhat.com

Hi Ben,

If there are two paths on a dm-1 say sda and sdb as below.

#  multipath -ll
	mpathd (3600110d001ee7f0102050001cc0b6751) dm-1 SANBlaze,VLUN MyLun
	size=8.0M features='0' hwhandler='0' wp=rw
	`-+- policy='round-robin 0' prio=50 status=active
	  |- 8:0:1:0  sda 8:48 active ready  running
	  `- 9:0:1:0  sdb 8:64 active ready  running          

And on sda if iam seeing lot of errors due to which the sda path is fluctuating from failed state to active state and vicevera.

My requirement is something like this if sda is failed for more then 5 times in a hour duration ,then I want to keep the sda in failed state for few hours (3hrs)

And the data should travel only thorugh sdb path.
Will this be possible with the below parameters.
Can you just let me know what values I should add for delay_watch_checks and delay_wait_checks.

Regards,
Muneendra.



-----Original Message-----
From: Muneendra Kumar M 
Sent: Thursday, December 22, 2016 11:10 AM
To: 'Benjamin Marzinski' <bmarzins@redhat.com>
Cc: dm-devel@redhat.com
Subject: RE: [dm-devel] deterministic io throughput in multipath

Hi Ben,

Thanks for the reply.
I will look into this parameters will do the internal testing and let you know the results.

Regards,
Muneendra.

-----Original Message-----
From: Benjamin Marzinski [mailto:bmarzins@redhat.com] 
Sent: Wednesday, December 21, 2016 9:40 PM
To: Muneendra Kumar M <mmandala@Brocade.com>
Cc: dm-devel@redhat.com
Subject: Re: [dm-devel] deterministic io throughput in multipath

Have you looked into the delay_watch_checks and delay_wait_checks configuration parameters?  The idea behind them is to minimize the use of paths that are intermittently failing.

-Ben

On Mon, Dec 19, 2016 at 11:50:36AM +0000, Muneendra Kumar M wrote:
>    Customers using Linux host (mostly RHEL host) using a SAN network for
>    block storage, complain the Linux multipath stack is not resilient to
>    handle non-deterministic storage network behaviors. This has caused many
>    customer move away to non-linux based servers. The intent of the below
>    patch and the prevailing issues are given below. With the below design we
>    are seeing the Linux multipath stack becoming resilient to such network
>    issues. We hope by getting this patch accepted will help in more Linux
>    server adoption that use SAN network.
> 
>    I have already sent the design details to the community in a different
>    mail chain and the details are available in the below link.
> 
>    [1]https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com_archives_dm-2Ddevel_2016-2DDecember_msg00122.html&d=DgIDAw&c=IL_XqQWOjubgfqINi2jTzg&r=E3ftc47B6BGtZ4fVaYvkuv19wKvC_Mc6nhXaA1sBIP0&m=vfwpVp6e1KXtRA0ctwHYJ7cDmPsLi2C1L9pox7uexsY&s=q5OI-lfefNC2CHKmyUkokgiyiPo_Uj7MRu52hG3MKzM&e= .
> 
>    Can you please go through the design and send the comments to us.
> 
>     
> 
>    Regards,
> 
>    Muneendra.
> 
>     
> 
>     
> 
> References
> 
>    Visible links
>    1. 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com_ar
> chives_dm-2Ddevel_2016-2DDecember_msg00122.html&d=DgIDAw&c=IL_XqQWOjub
> gfqINi2jTzg&r=E3ftc47B6BGtZ4fVaYvkuv19wKvC_Mc6nhXaA1sBIP0&m=vfwpVp6e1K
> XtRA0ctwHYJ7cDmPsLi2C1L9pox7uexsY&s=q5OI-lfefNC2CHKmyUkokgiyiPo_Uj7MRu
> 52hG3MKzM&e=

> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com_ma
> ilman_listinfo_dm-2Ddevel&d=DgIDAw&c=IL_XqQWOjubgfqINi2jTzg&r=E3ftc47B6BGtZ4fVaYvkuv19wKvC_Mc6nhXaA1sBIP0&m=vfwpVp6e1KXtRA0ctwHYJ7cDmPsLi2C1L9pox7uexsY&s=UyE46dXOrNTbPz_TVGtpoHl3J3h_n0uYhI4TI-PgyWg&e=

  parent reply	other threads:[~2016-12-26  9:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-19 11:50 deterministic io throughput in multipath Muneendra Kumar M
2016-12-19 12:09 ` Hannes Reinecke
2016-12-21 16:09 ` Benjamin Marzinski
2016-12-22  5:39   ` Muneendra Kumar M
2016-12-26  9:42   ` Muneendra Kumar M [this message]
2017-01-03 17:12     ` Benjamin Marzinski
2017-01-04 13:26       ` Muneendra Kumar M
2017-01-16 11:19       ` Muneendra Kumar M
2017-01-17  1:04         ` Benjamin Marzinski
2017-01-17 10:43           ` Muneendra Kumar M
2017-01-23 11:02           ` Muneendra Kumar M
2017-01-25  9:28             ` Benjamin Marzinski
2017-01-25 11:48               ` Muneendra Kumar M
2017-01-25 13:07                 ` Benjamin Marzinski
2017-02-01 11:58                   ` Muneendra Kumar M
2017-02-02  1:50                     ` Benjamin Marzinski
2017-02-02 11:48                       ` Muneendra Kumar M
2017-02-02 17:39                         ` Benjamin Marzinski
2017-02-02 18:02                           ` Muneendra Kumar M
2017-02-02 18:29                             ` Benjamin Marzinski
2017-02-03 11:43                               ` Muneendra Kumar M

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=8cd4cc5f20b540a1b8312ad485711152@BRMWP-EXMB12.corp.brocade.com \
    --to=mmandala@brocade.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.