<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: multipath recommended configuration in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/multipath-recommended-configuration/m-p/6774388#M54775</link>
    <description>&lt;P&gt;The MSA array is NOT an Active-Active Array.&lt;/P&gt;&lt;P&gt;So expect not all four sub-paths (sdXX) will be active. The array is active-passive so expect I/O to be on half the active paths only...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let me know if this clarifies the issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 12 Aug 2015 18:33:28 GMT</pubDate>
    <dc:creator>Alzhy</dc:creator>
    <dc:date>2015-08-12T18:33:28Z</dc:date>
    <item>
      <title>multipath recommended configuration</title>
      <link>https://community.hpe.com/t5/operating-system-linux/multipath-recommended-configuration/m-p/6707417#M54702</link>
      <description>&lt;P&gt;OS: SLES 11 SP 3 (kernel version: 3.0.x)&lt;/P&gt;&lt;P&gt;/dev/dm-0 comprises of sdg, sdq AND sdb, sdl&lt;BR /&gt;&lt;BR /&gt;If "path_grouping_policy" is set to "group_by_prio" then I observe(via iostat -xk /dev/dm-0) all I/O only on /dev/sdg and /dev/sdq, while sdb and sdl remains 100% idle.&lt;BR /&gt;But when "path_grouping_policy" is set to "multibus", then I can see that I/O is properly distributed on all the disks(sdg, sdq .. sdb, sdl).&lt;BR /&gt;&lt;BR /&gt;when "path_grouping_policy" is set to "group_by_prio" then running "multipath -ll" shows:&lt;/P&gt;&lt;PRE&gt;mpatha (3600c0ff0001e6435600e9b5401000000) dm-0 HP,MSA 2040 SAN
size=2.2T features='1 queue_if_no_path' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| |- 3:0:1:0  sdg 8:96  active ready running
| `- 4:0:1:0  sdq 65:0  active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
  |- 3:0:0:0  sdb 8:16  active ready running
  `- 4:0:0:0  sdl 8:176 active ready running&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;when "path_grouping_policy" is set to "multibus" then running "multipath -ll" shows:&lt;/P&gt;&lt;PRE&gt;mpatha (3600c0ff0001e6435600e9b5401000000) dm-0 HP,MSA 2040 SAN
size=2.2T features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=30 status=active
  |- 3:0:0:0  sdb 8:16  active ready running
  |- 3:0:1:0  sdg 8:96  active ready running
  |- 4:0:0:0  sdl 8:176 active ready running
  `- 4:0:1:0  sdq 65:0  active ready running&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please recommend me which one is recommended for best performance(group_by_prio vs multibus). Also /etc/multipath.conf on my system looks like:&lt;/P&gt;&lt;PRE&gt;defaults {
            polling_interval       10
            path_selector          "round-robin 0"
            path_grouping_policy   group_by_prio
            uid_attribute          "ID_SERIAL"
            prio                   alua   
            path_checker           tur    
            rr_min_io_rq           100
            flush_on_last_del      no
            max_fds                "max"
            rr_weight              uniform   
            failback               immediate
            no_path_retry          18    
            queue_without_daemon   no
            user_friendly_names    yes
            mode                   644
            uid                    0
            gid                    disk
}&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also is there any multipath driver available from HP for MSA 2040 for Linux(RHEL 7 and SLES 11 SP 3) ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Feb 2015 07:41:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/multipath-recommended-configuration/m-p/6707417#M54702</guid>
      <dc:creator>csrsupport</dc:creator>
      <dc:date>2015-02-11T07:41:25Z</dc:date>
    </item>
    <item>
      <title>Re: multipath recommended configuration</title>
      <link>https://community.hpe.com/t5/operating-system-linux/multipath-recommended-configuration/m-p/6774388#M54775</link>
      <description>&lt;P&gt;The MSA array is NOT an Active-Active Array.&lt;/P&gt;&lt;P&gt;So expect not all four sub-paths (sdXX) will be active. The array is active-passive so expect I/O to be on half the active paths only...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let me know if this clarifies the issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Aug 2015 18:33:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/multipath-recommended-configuration/m-p/6774388#M54775</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2015-08-12T18:33:28Z</dc:date>
    </item>
    <item>
      <title>Re: multipath recommended configuration</title>
      <link>https://community.hpe.com/t5/operating-system-linux/multipath-recommended-configuration/m-p/6996944#M55084</link>
      <description>&lt;P&gt;I managed to get both sp's active\active..&amp;nbsp; Just playing around with some perf tests to see if "round-robin" or "queue-lenght 0" works best.&amp;nbsp;&lt;/P&gt;&lt;P&gt;[root@-xen-01 ~]# multipath -ll&lt;BR /&gt;3600c0ff000296ed90974245a01000000 dm-1 HP ,MSA 2040 SAN&lt;BR /&gt;size=931G features='0' hwhandler='1 alua' wp=rw&lt;BR /&gt;`-+- policy='queue-length 0' prio=1 status=active&lt;BR /&gt;|- 1:0:1:1 sdc 8:32 active ready running&lt;BR /&gt;|- 1:0:3:1 sde 8:64 active ready running&lt;BR /&gt;|- 2:0:1:2 sdg 8:96 active ready running&lt;BR /&gt;`- 2:0:3:2 sdi 8:128 active ready running&lt;BR /&gt;3600c0ff000299fb77eeb245a01000000 dm-0 HP ,MSA 2040 SAN&lt;BR /&gt;size=931G features='0' hwhandler='1 alua' wp=rw&lt;BR /&gt;`-+- policy='queue-length 0' prio=1 status=active&lt;BR /&gt;|- 1:0:0:1 sdb 8:16 active ready running&lt;BR /&gt;|- 1:0:2:1 sdd 8:48 active ready running&lt;BR /&gt;|- 2:0:0:2 sdf 8:80 active ready running&lt;BR /&gt;`- 2:0:2:2 sdh 8:112 active ready running&lt;BR /&gt;[root@xxx-xen-01 ~]#&lt;/P&gt;&lt;P&gt;device {&lt;BR /&gt;vendor "HP "&lt;BR /&gt;product "MSA 2040 SAN "&lt;BR /&gt;hardware_handler "1 alua"&lt;BR /&gt;path_selector "queue-length 0"&lt;BR /&gt;path_grouping_policy multibus&lt;BR /&gt;failback immediate&lt;BR /&gt;path_checker hp_sw&lt;BR /&gt;rr_weight priorities&lt;/P&gt;&lt;P&gt;__________________________________&lt;/P&gt;&lt;P&gt;round robin alua&lt;/P&gt;&lt;P&gt;[root@xxx-xen-02 sbin]# multipath -ll&lt;BR /&gt;3600c0ff000296ed90974245a01000000 dm-0 HP ,MSA 2040 SAN&lt;BR /&gt;size=931G features='0' hwhandler='1 alua' wp=rw&lt;BR /&gt;`-+- policy='round-robin 0' prio=1 status=active&lt;BR /&gt;|- 1:0:0:1 sdg 8:96 active ready running&lt;BR /&gt;|- 2:0:0:2 sdf 8:80 active ready running&lt;BR /&gt;|- 1:0:1:1 sde 8:64 active ready running&lt;BR /&gt;`- 2:0:3:2 sdi 8:128 active ready running&lt;BR /&gt;3600c0ff000299fb77eeb245a01000000 dm-1 HP ,MSA 2040 SAN&lt;BR /&gt;size=931G features='0' hwhandler='1 alua' wp=rw&lt;BR /&gt;`-+- policy='round-robin 0' prio=1 status=active&lt;BR /&gt;|- 1:0:2:1 sdd 8:48 active ready running&lt;BR /&gt;|- 2:0:1:2 sdb 8:16 active ready running&lt;BR /&gt;|- 1:0:3:1 sdc 8:32 active ready running&lt;BR /&gt;`- 2:0:2:2 sdh 8:112 active ready running&lt;BR /&gt;[root@xxx-xen-02 sbin]#&lt;/P&gt;&lt;P&gt;________________________________&lt;/P&gt;&lt;P&gt;device {&lt;BR /&gt;vendor "HP "&lt;BR /&gt;product "MSA 2040 SAN "&lt;BR /&gt;hardware_handler "1 alua"&lt;BR /&gt;path_selector "round-robin 0"&lt;BR /&gt;path_grouping_policy multibus&lt;BR /&gt;failback immediate&lt;BR /&gt;path_checker tur&lt;BR /&gt;rr_weight priorities&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Feb 2018 01:27:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/multipath-recommended-configuration/m-p/6996944#M55084</guid>
      <dc:creator>NAP_All41</dc:creator>
      <dc:date>2018-02-14T01:27:24Z</dc:date>
    </item>
  </channel>
</rss>

