search for: path_checker

Displaying 20 results from an estimated 21 matches for "path_checker".

2009 Sep 17
1
multipath using defaults rather than multipath.conf contents for some devices (?) - why ?
.../sbin/mpath_prio_alua /dev/%n" hardware_handler "0" path_selector "round-robin 0" path_grouping_policy group_by_prio failback immediate rr_weight uniform no_path_retry 18 rr_min_io 100 path_checker tur } - but our actual multipathing as shown by multipath -ll , and multipath -ll -v 3 looks as though for the HSV400 it is using the defaults rather than these settings. The defaults are #defaults { # udev_dir /dev # polling_interval 10 # selector...
2017 Jan 31
1
multipath show config different in CentOS 7?
...then I put something like this in multipath.conf devices { device { vendor "IBM" product "^1814" product_blacklist "Universal Xport" path_grouping_policy "group_by_prio" path_checker "rdac" features "0" hardware_handler "1 rdac" prio "rdac" failback immediate rr_weight "uniform" no_path_retry "12" } } In CentOS 6.x...
2013 Sep 18
3
multipathing XCP 1.6
Hello, I hope to be in the right list. my question is the following. I can''t seem to get multipathing configure on XCP 1.6. In XenCenter I was able to enable "Multipath" however, in the LUN under general tab I see " multipath 1 of 1 active", the the CLI I do the following command xe --m node session it list only one session. Can someone help me please? Thanks in
2009 Sep 27
0
SUMMARY : multipath using defaults rather than multipath.conf contents for some devices (?) - why ?
.../sbin/mpath_prio_alua /dev/%n" hardware_handler "0" path_selector "round-robin 0" path_grouping_policy group_by_prio failback immediate rr_weight uniform no_path_retry 18 rr_min_io 100 path_checker tur } - but our actual multipathing as shown by multipath -ll , and multipath -ll -v 3 looks as though for the HSV400 it is using the defaults rather than these settings. The defaults are #defaults { # udev_dir /dev # polling_interval 10 # selector...
2015 Feb 04
0
multipathd
...ce it. The V3700 complained that we were using the IBM's RDAC driver (true) and we were advised to change to using Linux multipath. I've done that but the default configuration for the DS3400s is: device { vendor IBM product 1726-4xx path_checker rdac features 1 queue_if_no_path hardware_handler 1 rdac prio_callout /sbin/mpath_prio_rdac /dev/%n no_path_retry 300 rr_min_io 1000 } The V3700 is still complaining and I note the "path checker rdac"...
2015 Feb 04
0
multipathd
.... I've done that but the default configuration for the DS3400s So you switched from IBM's proprietary multipath driver to the native Linux multipathing. Correct? > is: > device { > vendor IBM > product 1726-4xx > path_checker rdac > features 1 queue_if_no_path > hardware_handler 1 rdac > prio_callout /sbin/mpath_prio_rdac /dev/%n > no_path_retry 300 > rr_min_io 1000 > } The right settings are documented here:...
2015 Feb 04
0
multipathd
...ce it. The V3700 complained that we were using the IBM's RDAC driver (true) and we were advised to change to using Linux multipath. I've done that but the default configuration for the DS3400s is: device { vendor IBM product 1726-4xx path_checker rdac features 1 queue_if_no_path hardware_handler 1 rdac prio_callout /sbin/mpath_prio_rdac /dev/%n no_path_retry 300 rr_min_io 1000 } The V3700 is still complaining and I note the "path checker rdac"...
2015 Feb 04
0
multipathd
...ce it. The V3700 complained that we were using the IBM's RDAC driver (true) and we were advised to change to using Linux multipath. I've done that but the default configuration for the DS3400s is: device { vendor IBM product 1726-4xx path_checker rdac features 1 queue_if_no_path hardware_handler 1 rdac prio_callout /sbin/mpath_prio_rdac /dev/%n no_path_retry 300 rr_min_io 1000 } The V3700 is still complaining and I note the "path checker rdac"...
2015 Feb 04
0
multipathd
...ce it. The V3700 complained that we were using the IBM's RDAC driver (true) and we were advised to change to using Linux multipath. I've done that but the default configuration for the DS3400s is: device { vendor IBM product 1726-4xx path_checker rdac features 1 queue_if_no_path hardware_handler 1 rdac prio_callout /sbin/mpath_prio_rdac /dev/%n no_path_retry 300 rr_min_io 1000 } The V3700 is still complaining and I note the "path checker rdac"...
2015 Feb 04
0
multipathd
...ce it. The V3700 complained that we were using the IBM's RDAC driver (true) and we were advised to change to using Linux multipath. I've done that but the default configuration for the DS3400s is: device { vendor IBM product 1726-4xx path_checker rdac features 1 queue_if_no_path hardware_handler 1 rdac prio_callout /sbin/mpath_prio_rdac /dev/%n no_path_retry 300 rr_min_io 1000 } The V3700 is still complaining and I note the "path checker rdac"...
2015 Feb 04
0
multipathd
...ce it. The V3700 complained that we were using the IBM's RDAC driver (true) and we were advised to change to using Linux multipath. I've done that but the default configuration for the DS3400s is: device { vendor IBM product 1726-4xx path_checker rdac features 1 queue_if_no_path hardware_handler 1 rdac prio_callout /sbin/mpath_prio_rdac /dev/%n no_path_retry 300 rr_min_io 1000 } The V3700 is still complaining and I note the "path checker rdac"...
2006 Apr 13
1
device-mapper multipath
...blacklist { devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*" devnode "^hd[a-z][[0-9]*]" devnode "^hda[0-9]*" devnode "^cciss!c[0-9]d[0-9]*[p[0-9]*]" } multipaths { multipath { wwid 222ea000155eadda4 alias stor path_grouping_policy multibus path_checker readsector0 path_selector "round-robin 0" failback immediate } } ================================================== The output from "multipath -v 3" of my CentOS machine is below: load path identifiers cache # # all paths in cache : # 222ea000155eadda4 0:0:0:0 sda 8:0...
2015 Feb 05
0
UC multipathd
...m IBM's proprietary multipath driver to the native >Linux multipathing. Correct? Yes. We were told to do so by the suppliers of the V3700. > >> is: >> device { >> vendor IBM >> product 1726-4xx >> path_checker rdac >> features 1 queue_if_no_path >> hardware_handler 1 rdac >> prio_callout /sbin/mpath_prio_rdac /dev/%n >> no_path_retry 300 >> rr_min_io 1000 >> } > >The rig...
2015 Feb 05
0
UC multipathd
...m IBM's proprietary multipath driver to the native >Linux multipathing. Correct? Yes. We were told to do so by the suppliers of the V3700. > >> is: >> device { >> vendor IBM >> product 1726-4xx >> path_checker rdac >> features 1 queue_if_no_path >> hardware_handler 1 rdac >> prio_callout /sbin/mpath_prio_rdac /dev/%n >> no_path_retry 300 >> rr_min_io 1000 >> } > >The rig...
2015 Feb 05
0
UC multipathd
...m IBM's proprietary multipath driver to the native >Linux multipathing. Correct? Yes. We were told to do so by the suppliers of the V3700. > >> is: >> device { >> vendor IBM >> product 1726-4xx >> path_checker rdac >> features 1 queue_if_no_path >> hardware_handler 1 rdac >> prio_callout /sbin/mpath_prio_rdac /dev/%n >> no_path_retry 300 >> rr_min_io 1000 >> } > >The rig...
2015 Feb 05
0
UC multipathd
...m IBM's proprietary multipath driver to the native >Linux multipathing. Correct? Yes. We were told to do so by the suppliers of the V3700. > >> is: >> device { >> vendor IBM >> product 1726-4xx >> path_checker rdac >> features 1 queue_if_no_path >> hardware_handler 1 rdac >> prio_callout /sbin/mpath_prio_rdac /dev/%n >> no_path_retry 300 >> rr_min_io 1000 >> } > >The rig...
2015 Feb 05
0
UC multipathd
...m IBM's proprietary multipath driver to the native >Linux multipathing. Correct? Yes. We were told to do so by the suppliers of the V3700. > >> is: >> device { >> vendor IBM >> product 1726-4xx >> path_checker rdac >> features 1 queue_if_no_path >> hardware_handler 1 rdac >> prio_callout /sbin/mpath_prio_rdac /dev/%n >> no_path_retry 300 >> rr_min_io 1000 >> } > >The rig...
2015 Feb 05
0
UC multipathd
...m IBM's proprietary multipath driver to the native >Linux multipathing. Correct? Yes. We were told to do so by the suppliers of the V3700. > >> is: >> device { >> vendor IBM >> product 1726-4xx >> path_checker rdac >> features 1 queue_if_no_path >> hardware_handler 1 rdac >> prio_callout /sbin/mpath_prio_rdac /dev/%n >> no_path_retry 300 >> rr_min_io 1000 >> } > >The rig...
2008 Jun 25
6
dm-multipath use
Are folks in the Centos community succesfully using device-mapper-multipath? I am looking to deploy it for error handling on our iSCSI setup but there seems to be little traffic about this package on the Centos forums, as far as I can tell, and there seems to be a number of small issues based on my reading the dm-multipath developer lists and related resources. -geoff Geoff Galitz Blankenheim
2008 Apr 05
0
BUG(?): multipathd confusion leads to kernel panic in Xen 3.2.1-rc2
...{ udev_dir /dev polling_interval 2 selector "round-robin 0" path_grouping_policy multibus # getuid_callout "/sbin/scsi_id -g -u -s /block/%n" prio_callout /bin/true path_checker readsector0 rr_min_io 10 rr_weight priorities failback 2 no_path_retry fail user_friendly_name no } The default parameter node.conn[0].timeo.noop_out_interval = 10 on the initiator tells it...