search for: path_grouping_polici

Dear list, we have a relatively new Sun Storage 7310, where we connect CentOS 5.5 Servers (IBM LS21/LS41 Blades) via Brocade Switches, 4GBit FC. The Blades boot from SAN via qla2xxx, and have no harddisks at all. We want them to use multipathing from the very beginning, so /boot and / are already seen by multipathd. Problem is, that the Sun 7310 has two storage heads which run in

hi all We have a rh linux server connected to two HP SAN controllers, one an HSV200 (on the way out), the other an HSV400 (on the way in). (Via a Qlogic HBA). /etc/multipath.conf contains this : device { vendor "(COMPAQ|HP)" product "HSV1[01]1|HSV2[01]0|HSV300|HSV4[05]0" getuid_callout "/sbin/scsi_id -g -u -s /block/%n"

Hello, suppose I want to use a special configuration for my IBM/1814 storage array luns, 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

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

Hi all, I am trying to configure a failover multipath between 2 GNBD devices. I have a 4 nodes Redhat Cluster Suite (RCS) cluster. 3 of them are used for running services, 1 of them for central storage. In the future I am going to introduce another machine for central storage. The 2 storage machine are going to share/export the same disk. The idea is not to have a single point of failure

# cat /etc/redhat-release CentOS Linux release 7.1.1503 (Core) # uname -r 3.10.0-123.20.1.el7.x86_64 Hi, We use iSCSI over a 10G Ethernet Adapter and SRP over an Infiniband adapter to provide multipathing to our storage: # lspci | grep 10-Gigabit 81:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) 81:00.1 Ethernet controller: Intel Corporation

The reason for the behaviour observed below turned out to be that the device entry in /etc/multipath.conf was inadvertently appended *after* the devices section , rather than inside it - so that we had #devices { # device { # blah blah # } (file has a bunch of defaults commented out) # etc #} # # device { our settings } *rather than*

I am attempting to get multipath working with device-mapper (CentOS 4.2 and 4.3). It works on EVERY install of mine from RH (also v4.2, 4.3), but the same multipath.conf imported to all my installs of CentOS do not work. Note that I have tested a working 4.2 configuration file from RH on CentOS 4.2 and a working 4.3 configuration (it changed slightly) on CentOS 4.3. Neither worked. Our production

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

Hi all. While playing with iSCSI Enterprise Target + multipathd on CentOS 5.1 (both the target and the initiator/multipath/xen box are Cent 5.1), I encountered a strange fault condition that leads to a kernel panic in a version of Xen 3.2.1-rc2 pulled from a couple of days ago. My lab consists of two Clovertown machines with dual GigE into separate switches. The target box is softraid5

Hello, today I noticed the following on *only* one node: ----- cut here ----- Apr 29 11:01:18 node06 kernel: [2569440.616036] INFO: task ocfs2_wq:5214 blocked for more than 120 seconds. Apr 29 11:01:18 node06 kernel: [2569440.616056] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 29 11:01:18 node06 kernel: [2569440.616080] ocfs2_wq D