Bug 1127693
Summary: | Cluster activation/deactivation switches not working as a user might expect (-aen/-aly specifically) | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Nenad Peric <nperic> |
Component: | lvm2 | Assignee: | Peter Rajnoha <prajnoha> |
lvm2 sub component: | Activating existing Logical Volumes (RHEL6) | QA Contact: | cluster-qe <cluster-qe> |
Status: | CLOSED WONTFIX | Docs Contact: | |
Severity: | unspecified | ||
Priority: | unspecified | CC: | agk, heinzm, jbrassow, msnitzer, prajnoha, prockai, zkabelac |
Version: | 6.6 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-06 11:17:13 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: |
Description
Nenad Peric
2014-08-07 11:06:37 UTC
(In reply to Nenad Peric from comment #0) > Expected results: > > -aen should 'exclusively deactivate' an LV, meaning that an expected ... > Another option would be that LVM prints out a warning message if -aen was > used on an LV which was not exclusively activated in the first place. > Something like "There are no exclusively activated LVs to deactivate". I'd go with this option to fix the issue. Or there's a third option as well - to forbid "-aen" completely and just allow the common "-an" to deactivate the volume. > > Second issue could be solved by informing a user that an activation of an LV > did NOT pass since it was blocked by filtering. I actually had a situation > where LVs did not want to get activated, and I did not know why, since I > forgot that I set the volume_list tag in lvm.conf. Would have saved me some > debugging if LVM just told me that my LV cannot be activated on this node > due to the filters I forgot I had set in lvm.conf. > And the same applies to non-clustered lvchange -ay in case the LV does not pass the volume_list - this is reported only in verbose output (lvchange -ay -v ...). However, with clustered LVs, we don't even have this verbose output available for the lvchange command... So yes, we should improve messages here a bit. (In reply to Peter Rajnoha from comment #2) > > > > Second issue could be solved by informing a user that an activation of an LV > > did NOT pass since it was blocked by filtering. I actually had a situation > > where LVs did not want to get activated, and I did not know why, since I > > forgot that I set the volume_list tag in lvm.conf. Would have saved me some > > debugging if LVM just told me that my LV cannot be activated on this node > > due to the filters I forgot I had set in lvm.conf. > > > > And the same applies to non-clustered lvchange -ay in case the LV does not > pass the volume_list - this is reported only in verbose output (lvchange -ay > -v ...). > However, with clustered LVs, we don't even have this verbose output > available for the lvchange command... So yes, we should improve messages > here a bit. (Related bug #1023063, though that one is for RHEL7 and lvcreate, but the nature of the problem is the same.) We haven't looked at this one yet at all, adding "Devel Conditional NAK Design". Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com/ |