Back to bug 1007406

Who When What Removed Added
Peter Rajnoha 2013-09-12 12:32:13 UTC Status NEW POST
Peter Rajnoha 2013-09-12 12:32:58 UTC Assignee lvm-team prajnoha
Corey Marthaler 2013-09-12 14:06:02 UTC CC cmarthal
Peter Rajnoha 2013-09-12 14:12:23 UTC Status POST MODIFIED
Fixed In Version lvm2-2.02.100-3.el6
errata-xmlrpc 2013-09-12 14:33:19 UTC Status MODIFIED ON_QA
Bill Nottingham 2013-09-12 19:01:05 UTC CC extras-orphan
Nenad Peric 2013-10-15 14:01:09 UTC Status ON_QA VERIFIED
CC nperic
Peter Rajnoha 2013-11-05 08:45:32 UTC Doc Text When using MD RAID devices as PVs on top of which LVM logical volumes are defined and while lvmetad is enabled at the same time (global/use_lvmetad=1 lvm.conf setting), the accompanying logical volume autoactivation that is used together with lvmetad could cause dangling incomplete device-mapper devices representing logical volumes to be left in the system. This also kept the system in inconsistent state where the logical volumes could not be activated any further without manual cleanup of the dangling device-mapper devices. This was caused by triggering the LVM autoactivation at improper time during MD RAID array setup or deactivation. When the MD RAID arrays is not yet set up completely or it is being deactivated, the LVM logical volume activation fails. This has been fixed and the LVM logical volume is autoactivation at proper time only when the MD RAID device is ready for use.
Peter Rajnoha 2013-11-05 08:47:47 UTC Doc Text When using MD RAID devices as PVs on top of which LVM logical volumes are defined and while lvmetad is enabled at the same time (global/use_lvmetad=1 lvm.conf setting), the accompanying logical volume autoactivation that is used together with lvmetad could cause dangling incomplete device-mapper devices representing logical volumes to be left in the system. This also kept the system in inconsistent state where the logical volumes could not be activated any further without manual cleanup of the dangling device-mapper devices. This was caused by triggering the LVM autoactivation at improper time during MD RAID array setup or deactivation. When the MD RAID arrays is not yet set up completely or it is being deactivated, the LVM logical volume activation fails. This has been fixed and the LVM logical volume is autoactivation at proper time only when the MD RAID device is ready for use. When using MD RAID devices as PVs on top of which LVM logical volumes are defined and while lvmetad is enabled at the same time (global/use_lvmetad=1 lvm.conf setting), the accompanying logical volume autoactivation that is used together with lvmetad could cause dangling incomplete device-mapper devices representing logical volumes to be left in the system. This also kept the system in inconsistent state where the logical volumes could not be activated any further without manual cleanup of the dangling device-mapper devices. This was caused by triggering the LVM autoactivation at improper time during MD RAID array setup or deactivation. When the MD RAID array is not yet set up completely or it is being deactivated, the autoactivation of LVM logical volumes on top of it fails. This has been fixed and the LVM logical volume is autoactivation at proper time only when the MD RAID device is ready for use.
Peter Rajnoha 2013-11-05 08:49:07 UTC Doc Text When using MD RAID devices as PVs on top of which LVM logical volumes are defined and while lvmetad is enabled at the same time (global/use_lvmetad=1 lvm.conf setting), the accompanying logical volume autoactivation that is used together with lvmetad could cause dangling incomplete device-mapper devices representing logical volumes to be left in the system. This also kept the system in inconsistent state where the logical volumes could not be activated any further without manual cleanup of the dangling device-mapper devices. This was caused by triggering the LVM autoactivation at improper time during MD RAID array setup or deactivation. When the MD RAID array is not yet set up completely or it is being deactivated, the autoactivation of LVM logical volumes on top of it fails. This has been fixed and the LVM logical volume is autoactivation at proper time only when the MD RAID device is ready for use. When using MD RAID devices as PVs on top of which LVM logical volumes are defined and while lvmetad is enabled at the same time (global/use_lvmetad=1 lvm.conf setting), the accompanying logical volume autoactivation that is used together with lvmetad could cause dangling incomplete device-mapper devices representing logical volumes to be left in the system. This also kept the system in inconsistent state where the logical volumes could not be activated any further without manual cleanup of the dangling device-mapper devices. This was caused by triggering the LVM autoactivation at improper time during MD RAID array setup or deactivation. When the MD RAID array is not yet set up completely or it is being deactivated, the autoactivation of LVM logical volumes on top of it fails. This has been fixed and the LVM logical volume is autoactivated at proper time only when the MD RAID device is ready for use.
errata-xmlrpc 2013-11-21 23:28:17 UTC Status VERIFIED CLOSED
Resolution --- ERRATA
Last Closed 2013-11-21 18:28:17 UTC

Back to bug 1007406