Bug 1619226

Summary:	lvm2 seems to be doing automatic partial activation in Dracut
Product:	[Fedora] Fedora	Reporter:	Zdenek Kabelac <zkabelac>
Component:	lvm2	Assignee:	LVM Team <lvm-team>
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	agk, anprice, bmarzins, bmr, cfeist, heinzm, jonathan, kzak, lvm-team, mcsontos, msnitzer, prajnoha, zkabelac
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
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:		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 Zdenek Kabelac 2018-08-20 11:34:24 UTC

Description of problem:

While looking on some other issue - there seems to be several bugs present while booting and activating lvm2 in Dracut.

It looks like there is a path that lvm2 with 'read-only' locking type activation (4) is able to activate  root LV in partial mode - so some missing PVs are automatically replaced with 'error' segments.

This seems to look like serious bug - as the activation itself is not traced by change of VG metadata when PV is really missing, and LV can get active with replaced error segments without sign of indication of any problem.

Assumption is - the partial mode was 'misused' to allow proceeding with activation of mirror/raid  LVs when individual legs get missing - while this feature is a degraded mode activation - it's getting mixes inside lvm2 with partial mode.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ben Cotton 2019-08-13 17:13:26 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 2 Ben Cotton 2019-08-13 19:42:43 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 3 Ben Cotton 2020-11-03 15:01:54 UTC

This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Zdenek Kabelac 2020-11-03 18:15:38 UTC

Still unresolved - keeping for Rawhide.