Bug 1023063
Summary: | Trying to create an LV on a cluster which is not allowed by volume_list filter causes non-understandable errors | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Nenad Peric <nperic> | ||||||
Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> | ||||||
lvm2 sub component: | Default / Unclassified | QA Contact: | cluster-qe <cluster-qe> | ||||||
Status: | CLOSED CURRENTRELEASE | Docs Contact: | |||||||
Severity: | unspecified | ||||||||
Priority: | unspecified | CC: | agk, cmarthal, heinzm, jbrassow, msnitzer, prajnoha, prockai, thornber, vincent.y.chen, zkabelac | ||||||
Version: | 7.0 | ||||||||
Target Milestone: | rc | ||||||||
Target Release: | --- | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | lvm2-2.02.114-2.el7.x86_64 | Doc Type: | Bug Fix | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2014-12-04 21:55:54 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 1140821 | ||||||||
Attachments: |
|
Created attachment 815812 [details]
lvcreate debug message
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. 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. (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. thanks, Perter. I think i understand the reason. 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. [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