Back to bug 1382688

Who When What Removed Added
Prasanth 2016-10-07 20:58:02 UTC CC pprakash
Peter Rajnoha 2016-10-10 10:53:14 UTC Status NEW POST
Peter Rajnoha 2016-10-10 10:56:31 UTC Assignee lvm-team prajnoha
Corey Marthaler 2016-10-10 13:38:32 UTC CC cmarthal
Mark Thacker 2016-10-11 00:20:17 UTC CC mthacker
Marcel Kolaja 2016-10-11 11:10:08 UTC CC mkolaja, snagar
Flags needinfo?(snagar)
Siddharth Nagar 2016-10-11 19:31:09 UTC Priority unspecified urgent
Flags needinfo?(snagar)
Tom Lavigne 2016-10-11 21:06:41 UTC CC tlavigne
Tom Lavigne 2016-10-11 22:18:38 UTC Blocks 1383833
Tom Lavigne 2016-10-11 22:19:35 UTC Keywords ZStream
Steve Almy 2016-10-12 00:24:51 UTC CC salmy
Zhang Yi 2016-10-12 01:17:16 UTC CC yizhan
Lucie Vařáková 2016-11-04 14:13:09 UTC CC prasun.gera
CC lmanasko
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>
Doc Type If docs needed, set a value Bug Fix
John Skeoch 2016-11-08 03:54:17 UTC CC sashinde
John Skeoch 2016-11-18 04:10:36 UTC CC sashinde mzywusko
Milan Navratil 2017-03-14 17:10:23 UTC Docs Contact mnavrati
Marian Csontos 2017-03-28 15:41:14 UTC Status POST MODIFIED
Fixed In Version lvm2-2.02.169-1.el7
errata-xmlrpc 2017-03-28 15:47:04 UTC Status MODIFIED ON_QA
Roman Bednář 2017-04-11 09:41:31 UTC Status ON_QA VERIFIED
CC rbednar
Pasi Karkkainen 2017-04-25 09:11:57 UTC CC pasik
Milan Navratil 2017-05-22 10:10:57 UTC 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>
LVM2 library incompatibilities no longer cause device monitoring to fail and be lost during an upgrade

Due to a bug in the lvm2-2.02.166-1.el package, released in Red Hat Enterprise Linux 7.3, the library was incompatible with earlier versions of Red Hat Enterprise Linux 7. The incompatibility could cause device monitoring to fail and be lost during an upgrade. As a consequence, device failures could go unnoticed (RAID), or out-of-space conditions were not handled properly (thin-p). This update fixes the incompatibility, and the logical volume monitoring now works as expected.
Shivam Gupta 2017-07-31 16:54:47 UTC CC shivgupt
errata-xmlrpc 2017-08-01 21:49:49 UTC Status VERIFIED CLOSED
Resolution --- ERRATA
Last Closed 2017-08-01 17:49:49 UTC
Pavel Najman 2021-09-03 12:54:42 UTC Pool ID sst_platform_storage_rhel_7 sst_logical_storage_rhel_7

Back to bug 1382688