Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 815809[details]
clvmd -d2 log
Description of problem:
If you try to create an LV on a cluster node (locking_type 3, clvmd running) and you have volume_list defined which would normally not allow this LV to be created, LVM spits an error which makes very little sense.
Furthermore clvmd debugging messages are quite useless in this case, since there is nothing in them (used clvmd -d2)
Version-Release number of selected component (if applicable):
lvm2-2.02.103-2.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
Define volume_list with something you do not have on the system
try to create an LV on clustered VG
Actual results:
[root@host-050 ~]# lvcreate vg -n lv3 -l29
/dev/vg/lv3: not found: device not cleared
Aborting. Failed to wipe start of new LV.
Expected results:
A normal error, which makes sense :)
Like so (the error from single machine mode):
Not activating vg/lv3 since it does not pass activation filter.
Failed to activate new LV.
Additional info:
I am attaching -vvvv and clvmd log of failed creation
The message has changed now to:
[root@rhel7-b ~]# lvcreate -l1 vg
Volume "vg/lvol0" is not active locally.
Aborting. Failed to wipe start of new LV.
It should be in clvmd log as well, but it's too late now. Let's consider this for 7.1.
(In reply to vincent_chen from comment #4)
> Perter, i fail to create the cluster lvm with message you show above. what's
> the does message mean? i don't understand why i can't create cluster lvm.
The most common reason for this message is that you have activation/volume_list defined in your lvm.conf and that you're trying to create an LV which does not match this list.
We should still improve the message here - I understand the message we give now is still not perfect. The best would be if clvmd could send back an error code or the error/warning message directly describing what exactly happened. But for this to work we'd need to enhance clvmd protocol which is not easy at the moment since it would require considerable updates to it (which probably won't be backward compatible). So it's a bit more complex change. For this reason, we're giving these generic error messages on LVM command side.
Comment 9Jonathan Earl Brassow
2014-12-04 21:55:54 UTC
[root@bp-01 ~]# lvm dumpconfig | grep volume_list
volume_list=["vg/lv", "rhel_bp-01"]
[root@bp-01 ~]# lvcreate -L 200M -n lv vg
Logical volume "lv" created.
[root@bp-01 ~]# lvcreate -L 200M -n lv2 vg
Volume "vg/lv2" is not active locally.
Aborting. Failed to wipe start of new LV.
This is an improvement on the previous message. I am closing this bug "current release". If there is still a desire for improvement, you can reopen this bug and we will evaluate it for a future release.
Created attachment 815809 [details] clvmd -d2 log Description of problem: If you try to create an LV on a cluster node (locking_type 3, clvmd running) and you have volume_list defined which would normally not allow this LV to be created, LVM spits an error which makes very little sense. Furthermore clvmd debugging messages are quite useless in this case, since there is nothing in them (used clvmd -d2) Version-Release number of selected component (if applicable): lvm2-2.02.103-2.el7.x86_64 How reproducible: 100% Steps to Reproduce: Define volume_list with something you do not have on the system try to create an LV on clustered VG Actual results: [root@host-050 ~]# lvcreate vg -n lv3 -l29 /dev/vg/lv3: not found: device not cleared Aborting. Failed to wipe start of new LV. Expected results: A normal error, which makes sense :) Like so (the error from single machine mode): Not activating vg/lv3 since it does not pass activation filter. Failed to activate new LV. Additional info: I am attaching -vvvv and clvmd log of failed creation