From: finley@anl.gov
To: linux-lvm@redhat.com
Subject: [linux-lvm] multipath works; lvm on multipath does not
Date: Wed, 15 Jul 2009 16:53:17 -0500 (CDT) [thread overview]
Message-ID: <23821558.221921247694797978.JavaMail.root@zimbra> (raw)
In-Reply-To: <19502392.221881247694711520.JavaMail.root@zimbra>
How can I tell what is causing LVM on multipath volumes to fail, while direct multipath volumes are working?
The details:
I have several volumes that are multipathed over fibre channel (2 qlogic cards in the host) from a Fujitsu Eternus 4000 (4 controllers).
When using a file system mounted on the dm-multipath device directly (Ie.: generating I/O via IOZone), it fails over gracefully when I pull out either of the fibre pairs, and the file system continues to operate. This device is called /dev/mapper/zimbra-mb1-t2-v4_fujitsu1-lun66.
However, when I access an LVM volume created with sister devices as PVs, the LVM presented volume does not fail over. Rather the LV device goes inaccessible and the file system (ext3) re-mounts itself as read-only. If I try to access any of the underlying PVs, they still respond as available (Ie.: fdisk -l $PV).
I am not seeing duplicate devices, and am using the following filter in /etc/lvm/lvm.conf:
filter = [ "a|^/dev/md.*|", "a|^/dev/mapper/zimbra-mb.*-t.*-v.*_.*-lun.*|", "r|.*|" ]
I have also added the following, but dm-multipath devices seem usable by LVM with or without this setting:
types = [ "device-mapper", 1 ]
I have tried removing the /etc/lvm/cache/.cache file, but that seems to have had no effect. I've also tried re-building the initrd after modifying the lvm.conf file, also with no effect.
Additional info:
root@zimbra-mb1:~# pvs
PV VG Fmt Attr PSize PFree
/dev/mapper/zimbra-mb1-t1-v1_fujitsu1-lun55 mb1_t1 lvm2 a- 195.31G 60.31G
/dev/mapper/zimbra-mb1-t1-v2_fujitsu1-lun56 mb1_t1 lvm2 a- 195.31G 60.31G
/dev/mapper/zimbra-mb1-t1-v3_fujitsu1-lun57 mb1_t1 lvm2 a- 195.31G 60.31G
/dev/mapper/zimbra-mb1-t1-v4_fujitsu1-lun58 mb1_t1 lvm2 a- 195.31G 60.31G
/dev/mapper/zimbra-mb1-t2-v1_fujitsu1-lun63 mb1_t2 lvm2 a- 504.00G 4.00G
/dev/mapper/zimbra-mb1-t2-v2_fujitsu1-lun64 mb1_t2 lvm2 a- 488.28G 0
/dev/mapper/zimbra-mb1-t2-v3_fujitsu1-lun65 mb1_t2 lvm2 a- 195.31G 195.31G
/dev/mapper/zimbra-mb1-t2-v5_fujitsu1-lun67 mb1_t2 lvm2 a- 354.37G 0
/dev/mapper/zimbra-mb1-t2-v6_fujitsu1-lun68 mb1_t2 lvm2 a- 234.56G 77.21G
/dev/md1 zimbra-mb1 lvm2 a- 136.50G 83.50G
kernel version: 2.6.24-24-server
distoro: Ubuntu Hardy
multipath-tools: 0.4.8-7ubuntu2
lvm2: 2.02.26-1ubuntu9
Thanks!
-Brian
next parent reply other threads:[~2009-07-15 21:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19502392.221881247694711520.JavaMail.root@zimbra>
2009-07-15 21:53 ` finley [this message]
2009-07-15 22:11 ` [linux-lvm] multipath works; lvm on multipath does not Chandra Seetharaman
2009-07-15 22:22 ` Brian E. Finley
2009-07-15 23:07 ` Chandra Seetharaman
2009-07-15 23:26 ` malahal
2009-07-16 0:30 ` Brian Elliott Finley
2009-07-16 0:53 ` malahal
2009-07-16 2:08 ` Brian Elliott Finley
2009-07-16 2:35 ` malahal
2009-07-16 2:59 ` Brian Elliott Finley
2009-07-16 3:10 ` Brian Elliott Finley
2009-07-16 3:16 ` Brian Elliott Finley
2009-07-16 3:23 ` Brian Elliott Finley
2009-07-16 3:43 ` malahal
2009-07-16 3:43 ` malahal
2009-07-16 0:28 ` Brian Elliott Finley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=23821558.221921247694797978.JavaMail.root@zimbra \
--to=finley@anl.gov \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).