Bug 1780663
| Summary: | displaying volumes during deactivation/activation loops can lead to all kinds of "invalid" and "failed" stat and device messages | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Corey Marthaler <cmarthal> |
| Component: | lvm2 | Assignee: | David Teigland <teigland> |
| lvm2 sub component: | Activating existing Logical Volumes | QA Contact: | cluster-qe <cluster-qe> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | high | CC: | agk, heinzm, jbrassow, mcsontos, msnitzer, pasik, prajnoha, rhandlin, zkabelac |
| Version: | 8.2 | ||
| Target Milestone: | rc | ||
| Target Release: | 8.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.03.09-2.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-04 02:00:20 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
Corey Marthaler
2019-12-06 15:27:07 UTC
The messages are a natural and harmless result of running commands concurrently, and the log levels should be changed so they don't appear. This is not a new issue in general, it also appears in RHEL7 with or without lvmetad. It is a result of lvm creating a list of /dev entries (directly or from udev) at the start of a command, and then collecting more info about those devs (like its uuid or size), but in the meantime the dev has changed or gone away due to another lvm command, causing the messages. lvm does not use locking to "freeze" /dev while running because the entries are not really important. LVM will open /dev nodes that are important and that it's going to read or write. In those cases error messages are appropriate, so changing logging levels needs to be aware of that. Mainly two cases needed changing: not using the existing error_if_no_value to suppress noise in _get_sysfs_value, and dev_get_size not using the existing quiet option for dev_open to suppress noise in dev_name_confirmed(). fix in master https://sourceware.org/git/?p=lvm2.git;a=commit;h=957904933b2b0f94eddc6204ca2fa61e2df741a0 Fix verified in the latest rpms. We're no longer seeing this issue during long run activation/deactivation testing. kernel-4.18.0-211.el8 BUILT: Thu Jun 4 03:33:39 CDT 2020 lvm2-2.03.09-2.el8 BUILT: Fri May 29 11:29:58 CDT 2020 lvm2-libs-2.03.09-2.el8 BUILT: Fri May 29 11:29:58 CDT 2020 lvm2-dbusd-2.03.09-2.el8 BUILT: Fri May 29 11:32:49 CDT 2020 lvm2-lockd-2.03.09-2.el8 BUILT: Fri May 29 11:29:58 CDT 2020 boom-boot-1.2-1.el8 BUILT: Sun Jun 7 07:20:03 CDT 2020 device-mapper-1.02.171-2.el8 BUILT: Fri May 29 11:29:58 CDT 2020 device-mapper-libs-1.02.171-2.el8 BUILT: Fri May 29 11:29:58 CDT 2020 device-mapper-event-1.02.171-2.el8 BUILT: Fri May 29 11:29:58 CDT 2020 device-mapper-event-libs-1.02.171-2.el8 BUILT: Fri May 29 11:29:58 CDT 2020 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 (lvm2 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4546 |