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 856209 - Use vgchange -aay in rc.sysinit and netfs init script
Summary: Use vgchange -aay in rc.sysinit and netfs init script
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: initscripts
Version: 6.4
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-11 12:58 UTC by Peter Rajnoha
Modified: 2018-12-09 16:51 UTC (History)
5 users (show)

Fixed In Version: initscripts-9.03.32-1.el6
Doc Type: Bug Fix
Doc Text:
Cause: Calling vgchange -a y instead of vgchange -a ay in sysinit and netfs Consequence: All volumes were activated Fix: Call vgchange -a ay Result: With this setting, only the volumes that are declared to be activate are actually activated (see also rhbz #817866). If the list is not declared, all volumes are activated by default (which is the classic old way).
Clone Of:
Environment:
Last Closed: 2013-02-21 10:26:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
lvm patch (1.33 KB, patch)
2012-09-11 14:07 UTC, Lukáš Nykrýn
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 381313 0 None None None Never
Red Hat Product Errata RHBA-2013:0518 0 normal SHIPPED_LIVE initscripts bug fix and enhancement update 2013-02-20 21:29:01 UTC

Description Peter Rajnoha 2012-09-11 12:58:26 UTC
lvm2-2.02.97-2.el6 and higher contains code that supports auto-activation feature and "activation/auto_activation_volume_list" declared in lvm.conf. With this setting, only the volumes that are declared to be activate are actually activated (see also rhbz #817866). If the list is not declared, all volumes are activated by default (which is the classic old way).

For this feature to work correctly on boot as well, we need initscripts (the /etc/rc.sysinit and /etc/init.d/netfs script) to call:
 
    vgchange --sysinit -a ay

(instead of former "vgchange --sysinit -a y", the extra "a" in "-a ay" meaning "AutoActivate").

Since lower versions of lvm2 do not understand the new setting/activation scheme, we need initscripts to declare a proper dependency on this new lvm2 version in the spec file as well.

Comment 1 Lukáš Nykrýn 2012-09-11 14:07:31 UTC
Created attachment 611775 [details]
lvm patch

Comment 8 errata-xmlrpc 2013-02-21 10:26:10 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0518.html


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