After some additional testing I’ve checked that the problem is related with dm-multipath, using /dev/sd devices instead of the multipath devices everything went fine.
Is cmirror supposed to work fine with dm-multipath or is it not supported?, is this a bug?
linux-cluster-bounces redhat com [mailto:linux-cluster-bounces redhat com] On Behalf Of Moralejo, Alfredo
I’m testing clustered mirror with RHEL 5.3 and I’m finding weird behavior. I’ve installed and enabled cmirror and created a couple of mirrored logical volumes (after some fight with clvmd errors…):
[root rmamseslab07 usr]# lvs -a -o +devices
lvol8 vg00 -wi-ao 4.00G /dev/cciss/c0d0p2(736)
lv_mirror vgcluster mwi-ao 1.00G lv_mirror_mlog 100.00 lv_mirror_mimage_0(0),lv_mirror_mimage_1(0)
[lv_mirror_mimage_0] vgcluster iwi-ao 1.00G /dev/mapper/mpath0p2(0)
[lv_mirror_mimage_1] vgcluster iwi-ao 1.00G /dev/mapper/mpqdiskp5(512)
[lv_mirror_mlog] vgcluster lwi-ao 4.00M /dev/mapper/mpath0p1(0)
lv_test1 vgcluster -wi-ao 1.00G /dev/mapper/mpqdiskp5(256)
lv_test4 vgcluster mwi-ao 1.00G lv_test4_mlog 100.00 lv_test4_mimage_0(0),lv_test4_mimage_1(0)
[lv_test4_mimage_0] vgcluster iwi-ao 1.00G /dev/mapper/mpqdiskp5(0)
[lv_test4_mimage_1] vgcluster iwi-ao 1.00G /dev/mapper/mpath0p2(256)
[lv_test4_mlog] vgcluster lwi-ao 4.00M /dev/mapper/mpath0p1(1)
[root rmamseslab07 usr]#
I’m simulating the failure of a disk by disabling one of the disks having a mirror leg from the storage array or from dm-multipath and the result I get is not the desired one, simply, any lvm command hangs and filesystem appears as hang as well. After enabling the disk again, everything is recovered.
Is anyone using successfully lvm mirror in a RH cluster with RHEL 5.3 with dm-multipath devices?
Is there any alternative for software mirroring to lvm mirror for RHCS. i.e. VxVM or something like that?
F. Hoffmann-La Roche Ltd.
Global Informatics Group Infrastructure
Phone: +34 91 305 97 87
Confidentiality Note: This message is intended only for the use of the named recipient(s) and may contain confidential and/or proprietary information. If you are not the intended recipient, please contact the sender and delete this message. Any unauthorized use of the information contained in this message is prohibited.