Bug 1732801
Summary: | Not all volume groups found at boot (intermittent) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tim Waugh <twaugh> |
Component: | lvm2 | Assignee: | David Teigland <teigland> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 30 | CC: | agk, anprice, bmarzins, bmr, cfeist, heinzm, jbrassow, jonathan, kzak, lvm-team, mcsontos, msnitzer, prajnoha, prockai, teigland, zkabelac |
Target Milestone: | --- | ||
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: | 2020-04-30 21:28:39 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: | |||
Attachments: |
Description
Tim Waugh
2019-07-24 11:52:31 UTC
Created attachment 1593122 [details]
LVM dump from 'good' boot, both VGs seen
Created attachment 1593131 [details]
LVM dump from 'bad' boot, both VGs seen
Created attachment 1593132 [details]
'journalctl -b -o cat' output from 'good' boot
Created attachment 1593133 [details]
'journalctl -b -o cat' output from 'bad' boot
We've been seeing a lot of cases like this and they are not all fixed yet. There have been some fixes that might help if you use a newer version. It looks like there's a newer version for f31 you might be able to try, but we should be making 2.03 versions of lvm available for fedora, so I'll look into that. Thanks. In case it's relevant: the Fedora 30 disk with the fedora_snoopy VG is SSD, but the RAID with the sometimes-missing fedora-server VG is made of HDDs and so is slower. Still seeing this regularly with lvm2-2.02.183-3.fc30.x86_64. No longer seeing this with lvm2-2.03.05-2.fc31.x86_64. This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. 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 '30'. 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 30 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. |