RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1044543 - lvm2: services specified with SYSTEMD_WANTS are not started for some LVM volumes
Summary: lvm2: services specified with SYSTEMD_WANTS are not started for some LVM volumes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lvm2
Version: 7.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: LVM and device-mapper development team
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1026860
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-18 14:16 UTC by Paul W. Frields
Modified: 2023-03-08 07:26 UTC (History)
26 users (show)

Fixed In Version: lvm2-2.02.103-8.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1026860
Environment:
Last Closed: 2014-06-13 11:48:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.