Bug 1658699

Summary: update lvm.conf settings
Product: Red Hat Enterprise Linux 8 Reporter: David Teigland <teigland>
Component: dracutAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: agk, bmr, dracut-maint-list, prajnoha
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-01 07:31:09 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:
Embargoed:

Description David Teigland 2018-12-12 17:08:29 UTC
Description of problem:

The lvm.conf in initramfs contains a number of settings that are no longer used.  We should discuss any lvm.conf changes you have needed to make in the past and decide if they can be dropped completely, or replaced with something different.

I'm not sure where the base file is coming from, but there are a number of settings (both commented and not) that are no longer used and no longer output from lvmconfig --type default, so once the base file is refreshed (from lvmconfig --type default --withcomments) a number of obsolete entries should disappear.

Some more specific comments on a few intentional changes I see:

1. locking_type. This setting is no longer used, I think you used it previously to tell lvm to avoid using file locks on the readonly fs.  This should be replaced with a command line option like --nolocking which is the simplest.
There's a complex mess of other options similar to nolocking that have been added over the years if there are some particular restrictions you want to apply to the command.  I can describe these if you are interested.

2. use_lvmetad: lvmetad no longer exists, and this setting doesn't do anything.

3. Do not run lvmetad update via pvscan in udev rule  - lvmetad is not running yet in dracut!

There's no more lvmetad, and I'm not entirely sure about the changes to 69-dm-lvm-metad.rules (which will be replaced by lvm-activation.rules).  If you were trying to avoid running the pvscan command entirely, then similar editing of the rule would be needed.  If you are intending to disable autoactivation, that is done by setting auto_activation_volume_list=[].  But maybe I'm not understanding the main issue this is trying to avoid.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 RHEL Program Management 2021-02-01 07:31:09 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.