Bug 1184353
| Summary: | default thin_check options don't have --clear-needs-check-flag | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Marian Csontos <mcsontos> |
| Component: | lvm2 | Assignee: | Peter Rajnoha <prajnoha> |
| lvm2 sub component: | Thin Provisioning (RHEL6) | QA Contact: | cluster-qe <cluster-qe> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | agk, heinzm, jbrassow, msnitzer, mspqa-list, nperic, prajnoha, prockai, thornber, vgoyal, zkabelac |
| Version: | 6.6 | ||
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.117-1.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Cause:
Missing build dependency caused default value for global/thin_check_options lvm.conf option to be incorrectly set during build time.
Consequence:
Default value for global/thin_check_options missed "--clear-needs-check-flag" option. This caused thin LVs to be still marked as needing a check while it was not necessary.
Fix:
Proper build dependency has been added which causes proper default value for global/thin_check_options to be set.
Result:
Default value for global/thin_check_options now includes "--clear-needs-check-flag" option.
|
Story Points: | --- |
| Clone Of: | 1184246 | Environment: | |
| Last Closed: | 2015-07-22 07:38:10 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: | 1184246 | ||
| Bug Blocks: | |||
|
Comment 2
Marian Csontos
2015-01-21 12:53:02 UTC
The default option found in the new lvm.conf is:
# thin_check_options = [ "-q", "--clear-needs-check-flag" ]
commented out options are considered default.
Marking this VERIFIED with:
lvm2-2.02.118-1.el6.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1411.html |