search for: user_friendly_nam

...uration of this host we have had varying combinations of the mapping of HBA to an enumerated /sys node. e.g.: host0 host2 host3 or host1 host3 host4 other combinations, etc. This messes up our multipath filtering for weightedpath priority settings. From /etc/multipath.conf: defaults { user_friendly_names no find_multipaths yes prio weightedpath prio_args "hbtl 0:.:.:.* 1 [1-9]:.:.:.* 10" path_grouping_policy group_by_prio path_selector "service-time 0" failback immediate polling_interval 5 no_path_retry 12 } The...

...or accessing these disks I use dm-multipath, since I use 2 separate networks for access. For these reasons I want host system to force not to scan dm-multipath disks for partitions. According to multipath.conf man there should be feature to do it defaults { find_multipaths yes user_friendly_names no # features "1 no_partitions" } However when I try this error: Dec 8 21:45:40 vnode4 kernel: device-mapper: table: 253:41: multipath: Unrecognised multipath feature request Dec 8 21:45:40 vnode4 kernel: device-mapper: table: 253:41: multipath: Unrecognised multipath featu...

...evice-mapper-multipath-0.4.9-64.el6_4.2.x86_64 device-mapper-multipath-libs-0.4.9-64.el6_4.2.x86_64 device-mapper-persistent-data-0.1.4-1.el6.x86_64 ~> sudo cat /etc/multipath.conf multipaths { multipath { wwid <redacted> alias <redacted> } } defaults { find_multipaths yes user_friendly_names yes } ~> sudo multipath -ll <redacted> (<redacted>) dm-1 HP,P2000G3 FC/iSCSI size=1.3T features='1 queue_if_no_path' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=130 status=active | |- 2:0:0:12 sdd 8:48 active ready running | `- 1:0:0:12 sdb 8:16 ac...

Hi all, Writing up some Fedora documentation, and looking to figure out the best way of mapping multipath network(!) LUNs to pools in libvirt. ie Infiniband SRP LUNs, but would probably apply to Fibre Channel equally as well. There are two approaches I can think of easily: a) Large LUNs (ie TB+) that are mapped to a host server as disk, with each LUN being configured as an LVM

...Port : 14567 State : Open Connected Clear Readonly : No Sectors : 41941688 # After, I have configured the device-mapper multipath by commenting the "blacklist" section in /etc/multipath.conf and adding this "defaults" section: defaults { user_friendly_names yes polling_interval 5 #path_grouping_policy failover path_grouping_policy multibus rr_min_io 1 failback immediate #failback manual no_path_retry fail #no_path_retry queue } Now I have the mpath device configured correct...

The most recent message is: [3108269.919256] sd 2:0:1:0: timing out command, waited 1080s [3108269.919528] sd 2:0:1:0: [sdb] Unhandled error code [3108269.919535] sd 2:0:1:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_OK [3108269.919540] sd 2:0:1:0: [sdb] CDB: Read(10): 28 00 00 01 21 47 00 00 08 00 [3108269.919586] EXT4-fs error (device sdb1): ext4_find_entry: reading directory #2 offset 0

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

..."/sbin/scsi_id -g -u -s /block/%n" # prio_callout /bin/true # path_checker readsector0 # rr_min_io 100 # rr_weight priorities # failback immediate # no_path_retry fail # user_friendly_name yes and multipath -ll reports : . . [snip other HSV400 paths - all similar] mpath12 (3600508b40007518f0000900000520000) dm-1 HP,HSV400 [size=150G][features=0][hwhandler=0] \_ round-robin 0 [prio=1][active] \_ 0:0:5:9 sdab 65:176 [active][ready] \_ round-robin 0 [prio=1][enabled] \_ 0:0:...

...ut "/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 to "ping" the target once every 10 seconds, then per node.conn[0].timeo.noop_out_timeout = 15, wait 15 seconds before marking the target down. So most of the time it can figure out a pat...

..."/sbin/scsi_id -g -u -s /block/%n" # prio_callout /bin/true # path_checker readsector0 # rr_min_io 100 # rr_weight priorities # failback immediate # no_path_retry fail # user_friendly_name yes and multipath -ll reports : . . [snip other HSV400 paths - all similar] mpath12 (3600508b40007518f0000900000520000) dm-1 HP,HSV400 [size=150G][features=0][hwhandler=0] \_ round-robin 0 [prio=1][active] \_ 0:0:5:9 sdab 65:176 [active][ready] \_ round-robin 0 [prio=1][enabled] \_ 0:0:...