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 1383833 - lvm related failed messages observed during update of device-mapper-event with 7.3-RC-1.3
Summary: lvm related failed messages observed during update of device-mapper-event wit...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lvm2
Version: 7.3
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: rc
: ---
Assignee: LVM and device-mapper development team
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1382688
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-11 22:18 UTC by Tom Lavigne
Modified: 2021-09-03 12:50 UTC (History)
18 users (show)

Fixed In Version: lvm2-2.02.166-1.el7.1
Doc Type: Bug Fix
Doc Text:
Previously, a bug has been introduced in lvm2-2.02.166-1.el7 (Red Hat Enterprise Linux 7.3 GA), that caused library incompatibilities with previous versions of Red Hat Enterprise Linux 7. That incompatibility could cause device monitoring to fail and be lost during an upgrade. The result was, that logical volumes that require monitoring would not have it, which could ultimately result in device failures going unnoticed (RAID) or out-of-space conditions not being handled (thin-p). A fix has been applied that addresses the incompatible issues and allows logical volume monitoring to continue as expected. It is possible to check the whether logical volumes are being properly monitored by specifying the 'segmonitor' field to 'lvs'. # lvs -o name,attr,segtype,segmonitor vg LV Attr Type Monitor my_linear -wi-a----- linear my_raid1 rwi-a-r--- raid1 not monitored Logical volumes which need no monitoring will not list a monitor state. Logical volumes which should have monitoring will list either 'not monitored' or 'monitored'. Monitoring can be turned on at any time by issuing an 'lvchange': # lvchange --monitor y <VG>/<LV>
Clone Of: 1382688
Environment:
Last Closed: 2016-11-04 09:03:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2613 0 normal SHIPPED_LIVE lvm2 bug fix update 2016-11-03 16:24:36 UTC

Description Tom Lavigne 2016-10-11 22:18:38 UTC 
This bug has been copied from bug #1382688 and has been proposed
to be backported to 7.3 z-stream (EUS).
Comment 9 errata-xmlrpc 2016-11-04 09:03:38 UTC 
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, 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://rhn.redhat.com/errata/RHBA-2016-2613.html
Note You need to log in before you can comment on or make changes to this bug.