We're running VM's with KVM on several hosts. We're using a LV per VM.
Every night the LVM-volumes are snapshotted one-by-one. After saving the snapshotted volume to another server we need to remove the snapshot.
/sbin/lvremove -f /dev/someVG/snap-VMvolumeXYZ hangs sometimes.
On the 4 hosts we're using LVM this is the second time in 4 days.
It's impossible to kill this process and all other LVM-commands are freezing to from this moment.
I have to remove /dev/mapper/someVG-VMvolumeXYZ manualy to be able to use other LVM-commands again.
It seems that the devices is SUSPENDED.
# dmsetup info someVG-VMvolumeXYZ
Name: someVG-VMvolumeXYZ
State: SUSPENDED
/dev/mapper/hl-someVG-VMvolumeXYZ: open failed: No such file or directory
Tables present: None
Open count: 2
Event number: 0
Major, minor: 251, 9
Number of targets: 0
UUID: LVM-R6AybI9pE2adk8jBZuRc837oZl9Kh2k3p8WzNdpuyQT7zb1xfFb0pJ3CbdkNyx4K
Is there a way to remove this lock or suspended state? Rebooting the host will solve this probably, but thats not an option twice a week. There are 15 to 30 VM's running on these hosts.
Ubuntu 10.04.1 LTS
Kerlen 2.6.32-25-server and 2.6.32-24-server x86_64
lvm2 2.02.54-1ubuntu4.1
udev 151-12.2
libvirt-bin 0.7.5-5ubuntu27.7 0ubuntu16+ 0.12.3+ noroms+ 0ubun
kvm 1:84+dfsg-
We're running VM's with KVM on several hosts. We're using a LV per VM.
Every night the LVM-volumes are snapshotted one-by-one. After saving the snapshotted volume to another server we need to remove the snapshot.
/sbin/lvremove -f /dev/someVG/ snap-VMvolumeXY Z hangs sometimes.
On the 4 hosts we're using LVM this is the second time in 4 days.
It's impossible to kill this process and all other LVM-commands are freezing to from this moment.
I have to remove /dev/mapper/ someVG- VMvolumeXYZ manualy to be able to use other LVM-commands again.
It seems that the devices is SUSPENDED.
# dmsetup info someVG-VMvolumeXYZ hl-someVG- VMvolumeXYZ: open failed: No such file or directory dk8jBZuRc837oZl 9Kh2k3p8WzNdpuy QT7zb1xfFb0pJ3C bdkNyx4K
Name: someVG-VMvolumeXYZ
State: SUSPENDED
/dev/mapper/
Tables present: None
Open count: 2
Event number: 0
Major, minor: 251, 9
Number of targets: 0
UUID: LVM-R6AybI9pE2a
Is there a way to remove this lock or suspended state? Rebooting the host will solve this probably, but thats not an option twice a week. There are 15 to 30 VM's running on these hosts.
Using a search-engine on this matters gives a lot of results going back to 2006. Seems to be exactly the same. readlist. com/lists/ redhat. com/linux- lvm/0/422. html
Link: http://