Bug 484804

Summary: lvm2-monitor hangs if you have LVs on Virtual Disks
Product: Red Hat Enterprise Linux 5 Reporter: Hector Arteaga <hector.arteaga>
Component: lvm2Assignee: Petr Rockai <prockai>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 5.3CC: agk, antillon.maurizio, bzeranski, dwysocha, heinzm, iannis, jbrassow, mbroz, prockai
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-19 14:22:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Hector Arteaga 2009-02-09 23:51:58 UTC
Description of problem:
lvm2-monitor hangs if you have Logical volumes created on virtual disks on a Virtul Machine.  Essentially if you have logical volumes created on a logical volume presented to a VM as a VD the service hangs.

Version-Release number of selected component (if applicable):
RedHat 5.3  
lvm2-2.02.40-6.el5

How reproducible:
100% so far

Steps to Reproduce:
1.  Create a Linux (RH5.3) virtual machine
2.  on a storage device, create a logical volume
3.  Present that logical volume as a virtual disk to the VM created
4.  From the VM create a logical volume on the VD that you presented.
5.  Stop and restart the lvm2-monitor service on the host (not the VM)

Comment 1 Petr Rockai 2009-03-01 13:14:07 UTC
Hi,

I need some more data here.

1) Do you get anything interesting in syslog on the host?
2) Could you try enabling monitoring for the LV in question manually with lvchange --monitor y after taking monitoring down?
3) Do you have any mirrored or snapshotted LVs in the VG in question? Is the LV you are exporting to the virtual machine snapshotted or mirrored?

Thanks!

Comment 3 Petr Rockai 2010-05-19 14:22:44 UTC
Hi,

this has been NEEDINFO for over a year now. I'm closing this, in case you still experience the problem or run into it again, please reopen the bug.

Yours,
   Petr.