similar to: multipath recipe for an enclosure ?

Hi list! I have a server with dual port Qlogic iSCSI HBA. I set up the same LUN for both ports, and boot the CentOS installer with "linux mpath". Installer detects multipathing fine, and creates mpath0 device for root disk. Installation goes fine, and the system boots up and works fine after the install from the multipath root device. After install the setup is like this: LUN 0 on

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

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"

I have inherited a system set up with multipath, which is not something I have seen before so I could use some advice The system is a Dell R420 with 2 LSI SAS2008 HBAs, 4 internal disks, and a MD3200 storage array attached via SAS cables. Oh and CentOS 6 lsblk shows the following: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdd 8:48 0 931.5G 0 disk ??sdd1

I have 15x SAS drives in a Dell MD1000 enclosure, attached to an LSI 9200-16e. This has been working well. The system is boothing off of internal drives, on a Dell SAS 6ir. I just tried to add a second storage enclosure, with 15 more SAS drives, and I got a lockup during Loading Kernel. I got the same results, whether I daisy chained the enclosures, or plugged them both directly into the LSI

Hello, The message you posted to the List below contained file enclosure data and consequently was not posted to the List. You will notice that the enclosure is quite large and contains data that many mailer programs can't use. This enclosure also adds far too much 'useless' data to the already huge archive file. If you wish to share files such as photos of your project with the

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

I (work :) bought a USB2.0/Firewire enclosure and I had a little trouble with it until I came across this page http://people.freebsd.org/~maho/USB/comment/ku350a.txt after trying the sysctl things work well. I haven't tried the USB2.0 side of it, as I don't have any USB2.0 controllers. The Firewire bit works great too (quite a bit faster than USB1 :) The enclosure in question is made

We have 14 500GB PATA drives left over from another project. Given that ZFS seems to prefer working with jbod''s, does anyone know of an inexpensive enclosure with an fcal interface to host the disks? This message posted from opensolaris.org

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

[ Yes, SP^M'n the list with follow-ups to myself ;-] From: Bryan J. Smith > If you are building a new system with such storage requirements, > I would really push you towards a 3Ware Escalade 8006-2 or 8506-4. When cost is supreme, then just a Escalade 7006-2 or 8006-2 with (2) [P]ATA or [S]ATA drives is what you want. It only adds ~$125 to system cost. When you want to minimize

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*

Hi, we have SunFire X4140 connected to Dell MD1220 SAS enclosure, single path, MPxIO disabled, via LSI SAS9200-8e HBA. Disks are visible with sas-addresses such as this in "zpool status" output: NAME STATE READ WRITE CKSUM cuve ONLINE 0 0 0 mirror-0 ONLINE 0 0 0

Hello I am wondering if anyone este tried this. I Have few CentOS 6.2 systems that are running KVM virtual machines. As storage backend for them I use 2 iscsi targets (based on openindiana). For 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

Hopefully someone can help get multipath working inside a domU. I'm using Xen 4.2.3 on a SLES 11 dom0, and both a SLES11 domU and a CentOS 6 domU. I'm using NPIV to connect my SAN disks to my domU, and, due to the way my SAN presents the LUNs, need to use multipath inside the domU. I've tried this on both SLES11 and CentOS6 with pretty much the same result. The root issue seems to

CentOS Errata and Enhancement Advisory 2018:0142 Upstream details at : https://access.redhat.com/errata/RHEA-2018:0142 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 52fcc4a771585ce8e80889c9b6c0a38dc3790a1cdc6e8935e1fa62e071cd4f61 device-mapper-multipath-0.4.9-111.el7_4.2.x86_64.rpm

CentOS Errata and Enhancement Advisory 2018:2464 Upstream details at : https://access.redhat.com/errata/RHEA-2018:2464 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: cf13f936fe22315827e3389260cc08aeca4d9081280e37c88fa8a9d98fd9142b device-mapper-multipath-0.4.9-119.el7_5.1.x86_64.rpm

CentOS Errata and Enhancement Advisory 2020:5022 Upstream details at : https://access.redhat.com/errata/RHEA-2020:5022 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 43561875a5de2607f06bea160d4eb38c49eb95d2de1193d32c75d69bbef928de device-mapper-multipath-0.4.9-134.el7_9.x86_64.rpm

Using CentOS 5.1, though with a few hours work I could update to 5.2.. I can install to SAN with a single path no problem but I'd like to be able to use dm-multipath. From the kickstart docs it seems this is supported but there is no information as to what the various options mean http://www.centos.org/docs/5/html/5.1/Installation_Guide/s1-kickstart2-options.html -- multipath (optional)

Hi Folks, When I boot ISOLinux, the locally attached disk is visible but the PATA 40 Gig in a USB attached enclosure is not. The locally attached disk has no bearing on what I am doing and to avoid confusion will not be mentioned again. Everything is happening on the 40 Gig. Let me explain. The goal is: Copy an installation iso to the disk, boot the disk and install it on that disk. I have