Bug 1087648
| Summary: | auto extension of thin pools that have passed their threshold with the "default" profile doesn't appear to work | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Corey Marthaler <cmarthal> | ||||||
| Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> | ||||||
| lvm2 sub component: | Thin Provisioning | QA Contact: | Cluster QE <mspqa-list> | ||||||
| Status: | CLOSED NOTABUG | Docs Contact: | |||||||
| Severity: | high | ||||||||
| Priority: | unspecified | CC: | agk, cmarthal, heinzm, jbrassow, msnitzer, prajnoha, prockai, thornber, zkabelac | ||||||
| Version: | 7.0 | ||||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-04-15 14:46: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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Corey Marthaler
2014-04-14 23:24:06 UTC
Created attachment 886317 [details]
-vvvv of the lvcreate w/ "default" profile
Created attachment 886318 [details]
-vvvv of the lvcreate w/ "thin-performance" profile
The default.profile defines activation/thin_pool_autoextend_threshold = 100 In case you use thin-performance.profile, this value is not defined in the profile and hence the "master" value defined in lvm.conf is used then. What's the value of activation/thin_pool_autoextend_threshold in your lvm.conf file? If it's other than 100, then it would explain the behaviour as reported here. Hint: if you want to see the exact configuration used by LVM (merged lvm.conf and profile config), you can use: lvm dumpconfig --profile <some_profile> --mergedconfig The test case knows how to properly turn on the autoextend threshold, this is what's in the lvm.conf:
thin_pool_autoextend_threshold = 70
thin_pool_autoextend_percent = 20
But, you're saying that by then calling the "default" profile on the lvcreate cmd line that I'm overriding what's in the lvm.conf and using the "default" which is to have it turned off again?
So looks like I answered my own question, it does turn it back off. So not a bug I guess. Odd though.
lvm dumpconfig --profile default --mergedconfig
activation {
checks=0
udev_sync=1
udev_rules=1
verify_udev_operations=0
retry_deactivation=1
missing_stripe_filler="error"
use_linear_target=1
reserved_stack=64
reserved_memory=8192
process_priority=-18
raid_region_size=512
readahead="auto"
raid_fault_policy="warn"
mirror_log_fault_policy="allocate"
mirror_image_fault_policy="remove"
snapshot_autoextend_threshold=100
snapshot_autoextend_percent=20
thin_pool_autoextend_threshold=100
thin_pool_autoextend_percent=20
use_mlockall=0
monitoring=1
polling_interval=15
}
(In reply to Corey Marthaler from comment #7) > So looks like I answered my own question, it does turn it back off. So not a > bug I guess. Odd though. It's just an overlay of configs (a "config cascade"): direct config override on command line (the "--config" cmd option) ---> profile config (either "--profile" cmd option or the one attached in metadata) ---> tag config ---> /etc/lvm/lvm.conf ---> default value hardcoded in the LVM binary itself And evaluated from left to right. The first value found is used. The default.profile contains all profilable configuration settings with default values assigned. |