Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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

Summary:	lvm related failed messages observed during update of device-mapper-event with 7.3-RC-1.3
Product:	Red Hat Enterprise Linux 7	Reporter:	Tom Lavigne <tlavigne>
Component:	lvm2	Assignee:	LVM and device-mapper development team <lvm-team>
lvm2 sub component:	Thin Provisioning	QA Contact:	cluster-qe <cluster-qe>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	urgent	CC:	agk, cmarthal, heinzm, jbrassow, lmanasko, mjuricek, mkolaja, msnitzer, mthacker, pprakash, prajnoha, prockai, rcyriac, snagar, sraj, thornber, tlavigne, zkabelac
Version:	7.3	Keywords:	ZStream
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
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>	Story Points:	---
Clone Of:	1382688	Environment:
Last Closed:	2016-11-04 09:03:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1382688
Bug Blocks:

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