Bug 1044543

Summary: lvm2: services specified with SYSTEMD_WANTS are not started for some LVM volumes
Product: Red Hat Enterprise Linux 7 Reporter: Paul W. Frields <pfrields>
Component: lvm2Assignee: LVM and device-mapper development team <lvm-team>
lvm2 sub component: Default / Unclassified QA Contact: cluster-qe <cluster-qe>
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: medium    
Priority: medium CC: agk, bmarzins, bmr, cmarthal, dwysocha, heinzm, jbrassow, Jes.Sorensen, jreznik, kay, lnykryn, lpoetter, lvm-team, michele, mruckman, mschmidt, msekleta, msnitzer, nperic, plautrba, prajnoha, prockai, systemd-maint, thornber, vpavlin, zkabelac
Version: 7.0   
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: lvm2-2.02.103-8.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1026860 Environment:
Last Closed: 2014-06-13 11:48:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1026860    
Bug Blocks:    

Comment 1 Peter Rajnoha 2013-12-19 11:04:23 UTC 
To test this issue, just create an MD with LVM on top of it, for example:

  mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sda /dev/sdb
  pvcreate /dev/md0
  vgcreate vg /dev/md0
  lvcreate -l1 vg

Then try to reboot the system and check whether the lvm2-pvscan@<major>:<minor>.service is in active or inactive state (where the <major> and <minor> is the major and minor for the MD device). If the service is in loaded, but inactive state you're hitting the bug which also causes the LV to stay inactive (since the service that would activate it is not run properly).

You can check the state of the service by:
  systemctl status lvm2-pvscan@<major>:<minor>.service
  (or just grep for it: systemctl -a | grep lvm2-pvscan)

With the fix, the pvscan service should always be in active state when loaded.
Comment 5 Corey Marthaler 2014-04-11 22:31:19 UTC 
Marking verified (SanityOnly). I saw no problems running the operations listed in comment #1 a few times. 


3.10.0-116.el7.x86_64
lvm2-2.02.105-14.el7    BUILT: Wed Mar 26 08:29:41 CDT 2014
lvm2-libs-2.02.105-14.el7    BUILT: Wed Mar 26 08:29:41 CDT 2014
lvm2-cluster-2.02.105-14.el7    BUILT: Wed Mar 26 08:29:41 CDT 2014
device-mapper-1.02.84-14.el7    BUILT: Wed Mar 26 08:29:41 CDT 2014
device-mapper-libs-1.02.84-14.el7    BUILT: Wed Mar 26 08:29:41 CDT 2014
device-mapper-event-1.02.84-14.el7    BUILT: Wed Mar 26 08:29:41 CDT 2014
device-mapper-event-libs-1.02.84-14.el7    BUILT: Wed Mar 26 08:29:41 CDT 2014
device-mapper-persistent-data-0.3.0-1.el7    BUILT: Fri Mar 28 07:42:24 CDT 2014
cmirror-2.02.105-14.el7    BUILT: Wed Mar 26 08:29:41 CDT 2014
Comment 6 Ludek Smid 2014-06-13 11:48:49 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.