Back to bug 1383833
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Peter Rajnoha | 2016-10-12 09:12:28 UTC | Status | NEW | POST |
| Peter Rajnoha | 2016-10-12 11:24:17 UTC | Status | POST | MODIFIED |
| Fixed In Version | lvm2-2.02.166-1.el7.1 | |||
| errata-xmlrpc | 2016-10-12 11:30:45 UTC | Status | MODIFIED | ON_QA |
| Martin Juricek | 2016-10-14 08:28:00 UTC | Status | ON_QA | VERIFIED |
| CC | mjuricek | |||
| Rejy M Cyriac | 2016-10-20 07:30:05 UTC | CC | rcyriac | |
| Lucie Vařáková | 2016-10-26 11:52:43 UTC | CC | lmanasko | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Lucie Vařáková | 2016-10-26 13:22:23 UTC | Flags | needinfo?(tlavigne) | |
| Tom Lavigne | 2016-10-26 13:28:45 UTC | Flags | needinfo?(tlavigne) | needinfo?(jbrassow) |
| Tom Lavigne | 2016-10-26 13:30:02 UTC | Flags | needinfo?(prajnoha) | |
| Jonathan Earl Brassow | 2016-10-26 15:33:24 UTC | Doc Text | A bug was introduced that caused library incompatibilities between previous version of RHEL7 and RHEL7.3. This incompatibility can cause device monitoring to fail and be lost during an upgrade. The result is that logical volumes that require monitoring (mirror, RAID, thin-provisioning) for the purpose of alerting the user of problems and automatic handling of problems will not have it. Ultimately, this could result in device failures going unnoticed (RAID) or out-of-space conditions not being handled (thin-p). This fix addresses the incompatible library issues and allows logical volume monitoring to continue as expected. | |
| Flags | needinfo?(jbrassow) needinfo?(prajnoha) | |||
| Jonathan Earl Brassow | 2016-10-26 16:01:40 UTC | Doc Text | A bug was introduced that caused library incompatibilities between previous version of RHEL7 and RHEL7.3. This incompatibility can cause device monitoring to fail and be lost during an upgrade. The result is that logical volumes that require monitoring (mirror, RAID, thin-provisioning) for the purpose of alerting the user of problems and automatic handling of problems will not have it. Ultimately, this could result in device failures going unnoticed (RAID) or out-of-space conditions not being handled (thin-p). This fix addresses the incompatible library issues and allows logical volume monitoring to continue as expected. | A bug was introduced in lvm2-2.02.166-1.el7 (RHEL7.3 GA) that caused library incompatibilities with previous versions of RHEL7. This incompatibility can cause device monitoring to fail and be lost during an upgrade. The result is that logical volumes that require monitoring (mirror, RAID, thin-provisioning) for the purpose of alerting the user of problems and automatic handling of problems will not have it. Ultimately, this could result in device failures going unnoticed (RAID) or out-of-space conditions not being handled (thin-p). This fix in lvm2-2.02.166-1.el7.1 addresses the incompatible library 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> |
| errata-xmlrpc | 2016-11-02 18:30:40 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-11-04 09:03:38 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-11-04 05:03:38 UTC | |||
| Lucie Vařáková | 2016-11-04 14:11:54 UTC | Doc Text | A bug was introduced in lvm2-2.02.166-1.el7 (RHEL7.3 GA) that caused library incompatibilities with previous versions of RHEL7. This incompatibility can cause device monitoring to fail and be lost during an upgrade. The result is that logical volumes that require monitoring (mirror, RAID, thin-provisioning) for the purpose of alerting the user of problems and automatic handling of problems will not have it. Ultimately, this could result in device failures going unnoticed (RAID) or out-of-space conditions not being handled (thin-p). This fix in lvm2-2.02.166-1.el7.1 addresses the incompatible library 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> | 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> |
| Pavel Najman | 2021-09-03 12:50:57 UTC | Pool ID | sst_platform_storage_rhel_7 | sst_logical_storage_rhel_7 |
Back to bug 1383833