Bug 511093 - LVM Does not Properly Activate VGs on multipath Devices
Summary: LVM Does not Properly Activate VGs on multipath Devices
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: lvm2
Version: 5.3
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: LVM and device-mapper development team
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-13 15:55 UTC by Jonathan Steffan
Modified: 2011-10-21 16:27 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-21 16:27:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jonathan Steffan 2009-07-13 15:55:36 UTC
Description of problem:
After adding a filter to ensure that LVM does not access multipath member devices, the mpath device VGs and LVs are not properly activated on boot.

Version-Release number of selected component (if applicable):
lvm2-2.02.40-6.el5

How reproducible:
Always.

Steps to Reproduce:
1. I configure multipath devices.
2. Add filter to only look at the mpath devices:
/etc/lvm/lvm.conf:
filter = [ "a|/dev/mpath.*|", "r/.*/" ]
preferred_names = [ "^/dev/mpath/", "^/dev/mapper/mpath" ]

3. Setup LVM on mpath devices. Activate and mount. Configure fstab.
4. Reboot.
  
Actual results:
VGs/LVs are not active on reboot. Manual intervention post-boot is required.

Expected results:
VGs/LVs are activated, and able to be mounted via fstab.

Additional info:
Everything works if manually activated and mounted. With the filter removed, everything is properly activated, but multipath failover does not work correctly. LVM seems that is uses the non-mpath devices and then when paths are failed mounts start rejecting I/O. With the filter, everything works correctly with regards to multipathing but manual intervention post-boot is required to mount everything.

Comment 1 Jonathan Steffan 2009-08-07 04:00:27 UTC
This works as expected with 5.3.

Comment 2 Jonathan Steffan 2009-08-07 04:02:09 UTC
Sorry, this works as expected with a 5.4 beta kernel: http://people.redhat.com/dzickus/el5/

Comment 4 Milan Broz 2011-10-21 16:27:20 UTC
Seems this bug is fixed long time ago.


Note You need to log in before you can comment on or make changes to this bug.