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 990696 - commented out sections in lvm.con w/ uncommented out variables now causes warnings
Summary: commented out sections in lvm.con w/ uncommented out variables now causes war...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lvm2
Version: 6.5
Hardware: x86_64
OS: Linux
unspecified
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: 2013-07-31 19:24 UTC by Corey Marthaler
Modified: 2013-07-31 20:11 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-31 20:11:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Corey Marthaler 2013-07-31 19:24:53 UTC 
Description of problem:
This is a regression from rhel6.4. For any commented out section tags, any variable inside that section that's not also commented out, will cause a warning message.

From lvm.conf:

# allocation {

[...]
    # Changes made in version 2.02.85 extended the reach of the 'cling'
    # policies to detect more situations where data can be grouped
    # onto the same disks.  Set this to 0 to revert to the previous
    # algorithm.
    maximise_cling = 1

    # Set to 1 to guarantee that mirror logs will always be placed on
    # different PVs from the mirror images.  This was the default
    # until version 2.02.85.
    mirror_logs_require_separate_pvs = 0

    # Set to 1 to guarantee that thin pool metadata will always
    # be placed on different PVs from the pool data.
    thin_pool_metadata_require_separate_pvs = 0
[...]

#}

[root@taft-01 lvm]# lvs
  Configuration setting "vgmetadatacopies" invalid. It's not part of any section.
  Configuration setting "thin_pool_zero" invalid. It's not part of any section.
  Configuration setting "thin_pool_discards" invalid. It's not part of any section.
  Configuration setting "thin_pool_chunk_size" invalid. It's not part of any section.
  Configuration setting "thin_pool_metadata_require_separate_pvs" invalid. It's not part of any section.
  Configuration setting "mirror_logs_require_separate_pvs" invalid. It's not part of any section.
  Configuration setting "maximise_cling" invalid. It's not part of any section.
  LV      VG        Attr       LSize  Pool Origin Data%  Move Log Cpy%Sync Convert
  lv_home vg_taft01 -wi-ao----  9.94g                                             
  lv_root vg_taft01 -wi-ao---- 50.00g                                             
  lv_swap vg_taft01 -wi-ao----  7.81g                                             



Version-Release number of selected component (if applicable):
2.6.32-404.el6.x86_64
lvm2-2.02.100-0.35.el6    BUILT: Tue Jul 30 09:44:33 CDT 2013
lvm2-libs-2.02.100-0.35.el6    BUILT: Tue Jul 30 09:44:33 CDT 2013
lvm2-cluster-2.02.100-0.35.el6    BUILT: Tue Jul 30 09:44:33 CDT 2013
udev-147-2.46.el6    BUILT: Tue Jan 15 06:41:59 CST 2013
device-mapper-1.02.79-0.35.el6    BUILT: Tue Jul 30 09:44:33 CDT 2013
device-mapper-libs-1.02.79-0.35.el6    BUILT: Tue Jul 30 09:44:33 CDT 2013
device-mapper-event-1.02.79-0.35.el6    BUILT: Tue Jul 30 09:44:33 CDT 2013
device-mapper-event-libs-1.02.79-0.35.el6    BUILT: Tue Jul 30 09:44:33 CDT 2013
cmirror-2.02.100-0.35.el6    BUILT: Tue Jul 30 09:44:33 CDT 2013


How reproducible:
Everytime
Comment 1 Peter Rajnoha 2013-07-31 19:39:03 UTC 
This is supposed to be a feature, not a bug actually... We've added more lvm.conf checks and one of them is that the config should be defined properly It's not correct to keep dangling config settings without being in any section - this could pose a confusion as lvm just ignored such settings silently before, now it warns at least.
Comment 2 Peter Rajnoha 2013-07-31 19:42:34 UTC 
(...I've seen many times that people uncommented some settings, but they forgot to uncomment the section itself and expecting that the config they uncommented will do the change...)
Comment 3 Peter Rajnoha 2013-07-31 19:46:36 UTC 
If those extra checks are unwanted, it's possible to disable them by setting config/checks=0.
Comment 5 Corey Marthaler 2013-07-31 20:11:00 UTC 
OK, that works, unless I comment out the config section. HA HA! :)

#config {

    # If enabled, any LVM2 configuration mismatch is reported.
    # This implies checking that the configuration key is understood
    # by LVM2 and that the value of the key is of a proper type.
    # If disabled, any configuration mismatch is ignored and default
    # value is used instead without any warning (a message about the
    # configuration key not being found is issued in verbose mode only).
    checks = 0

    # If enabled, any configuration mismatch aborts the LVM2 process.
    abort_on_errors = 0

    # Directory where LVM looks for configuration profiles.
    profile_dir = "/etc/lvm/profile"
#}


[root@taft-01 lvm]# lvs
  Configuration setting "checks" invalid. It's not part of any section.
  Configuration setting "profile_dir" invalid. It's not part of any section.
  Configuration setting "abort_on_errors" invalid. It's not part of any section.
Note You need to log in before you can comment on or make changes to this bug.