[RHEL6.1] lvremove fails with "Can't remove open logical volume" for not opened LVs
Issue
- lvremove sometimes fails with the messages below for not opened LVs.
- phenomenon 1
# lvremove -f testvg/lv Can't remove open logical volume "lv"
- phenomenon 2
# lvremove -f testvg/lv Unable to deactivate open testvg-lv (253:0) Unable to deactivate logical volume "lv"
- phenomenon 3
# lvremove -f testvg/lv LV testvg/lv in use: not deactivating Unable to deactivate logical volume "lv"
- phenomenon 1
- The phenomenon sometimes repeatedly occurs and the LV really looks to be opened by someone so unremovable.
- However, even just after the phenomenon, we cannot find any real opener. (Then, just by repeating lvremove, the LV can be removed soon.)
- The phenomenon confuses users and support venders very much, so lets them spend much time to investigate the reason.
- From a different aspect, applications using lvremove cannot handle the lvremove failure: applications cannot determine how many trials are needed to succeed lvremove, on the other hand, lvremove may never succeed due to a real opener resulting in an infinite loop.
Environment
- RHEL6.0
- kernel-2.6.32-71.el6
- udev-147-2.29.el6
- device-mapper-1.02.53-8.el6
- lvm2-2.02.72-8.el6
- udisks-1.0.1-2.el6
- RHEL6.1 Beta
- kernel-2.6.32-122.el6
- udev-147-2.34.el6
- device-mapper-1.02.62-2.el6
- lvm2-2.02.83-2.el6
- udisks-1.0.1-2.el6
- RHEL6.1 Snapshot2
- kernel-2.6.32-128.el6.x86_64
- udev-147-2.35.el6.x86_64
- device-mapper-1.02.62-3.el6.x86_64
- lvm2-2.02.83-3.el6.x86_64
- udisks-1.0.1-2.el6.x86_64
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.