Red Hat Bugzilla – Bug 167643
system-config-lvm unusable with lvm2-cluster installed but without cluster membership
Last modified: 2009-04-16 19:11:57 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc4 Firefox/1.0.6
Description of problem:
When lvm2-cluster is installed I get this error when trying to initialize a partition.
pvcreate command failed. Command attempted: "/usr/sbin/pvcreate -M 2 /dev/sdb1" - System Error Message: connect() failed on local socket: Connection refused
Locking type 2 initialisation failed.
I think the --ignorelockingfailure is needed for this to work properly.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install lvm2-cluster
2. Launch system-config-lvm
3. Try to initialize an entity
Actual Results: Got the error message above.
Expected Results: The partition should have become a physical volume.
It turns out that just about any time the GUI tries to get LVM information it
needs the --ignorelockingfailure flag. So if you have the GUI running and you
can see PVs or LVs, then you install lvm2-cluster
(lvm2-cluster-2.01.14-1.0.RHEL4 in this case) and do View->Reload, everything
will go back to Uninitialized Entities.
cLVM support in s-c-lvm is scheduled for RHEL4U3 (see bz159455).
Fix, until then, would amount to simple pop-up saying that clustered LVM is not
yet implemented, when cLVM configuration is detected.
Fixed in 1.0.4
Verified in 1.0.5-1.0.
QA_READY has been deprecated in favor of ON_QA. Please use ON_QA in the future.
Moving to ON_QA.
this should have been released in RHEL-4.2