- After wiping the multipath bindings file (through 'multipath -F' as well as removing the bindings file), and rebooting, the server returned with the LUNs in place, and mounted the file systems without issue; however LVM had them completely cross-mapped and corrupted.
- Red Hat Enterprise Linux 5 (RHEL5)
- This problem has been observed on RHEL5.7.
Boot from SAN system
- Devices are multipath'd using device-mapper-multipath-0.4.7-46.el5_7.1.
LVM2 boot disks, as well as non-boot volume groups using lvm2-2.02.84-6.el5_7.1
One of the devices making up a volume group is not a multipath device:
$ pvs -a -v | grep datavg PV VG Fmt Attr PSize PFree DevSize PV UUID /dev/mapper/mpath2p1 datavg lvm2 a- 2.00T 48.00G 2.00T rzkA95-BdOi-WfVd-Oebr-Baiy-1ncs-1FqPK7 /dev/mapper/mpath3p1 datavg lvm2 a- 1.00T 24.01G 1.00T m6Oy3T-4GKp-CKFc-7Kq3-ufKe-73IL-rjmT7z /dev/mapper/mpath4p1 datavg lvm2 a- 1.00T 24.01G 1.00T R3XTtG-INl4-y7J3-Zbq6-9euG-Bv3S-YYkK3W /dev/mapper/mpath5p1 datavg lvm2 a- 1.00T 24.01G 1.00T L02jvC-39hC-dVVb-QZ5J-AjP6-4c1U-sMKQLS /dev/mapper/mpath8p1 datavg lvm2 a- 2.00T 48.00G 2.00T ym2iEB-NT3K-y9la-jLxH-4iU1-sq3Q-WupfAk /dev/mapper/mpath9p1 datavg lvm2 a- 1.00T 24.01G 1.00T qSX7MV-Kpw3-W8gX-nWIJ-3ion-s1ln-J0pJdn /dev/sdp1 datavg lvm2 a- 500.07G 68.00M 500.07G WY2AN7-XdvN-wt8N-eL9s-Tcs4-O8S9-EALZ67 <--- sdp1 is not a multipath device
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.