Bug 1443438
Summary: | lvm: warning of thin pool capacity not working well | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Bruno Goncalves <bgoncalv> |
Component: | lvm2 | Assignee: | Zdenek Kabelac <zkabelac> |
lvm2 sub component: | Thin Provisioning | QA Contact: | Bruno Goncalves <bgoncalv> |
Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
Severity: | unspecified | ||
Priority: | unspecified | CC: | agk, heinzm, jbrassow, mcsontos, msnitzer, prajnoha, prockai, thornber, zkabelac |
Version: | 7.4 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | lvm2-2.02.171-2.el7 | Doc Type: | If docs needed, set a value |
Doc Text: |
In release regression bugfix, no doc needed
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-05-31 13:52:56 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
Bruno Goncalves
2017-04-19 09:23:05 UTC
Yep - we print only warning on the crossing of 80% threshold but not for later once - this will need further thinking as we on the other hand gained option to correctly work with thin-pool which has decreased its usage and crossed 80% again. But it should be possible to restore warning also for 85% and more percent again. Should be addressed by commit: 455a4de090f10f98ac2932a2540a30b7fdc34f61 https://www.redhat.com/archives/lvm-devel/2017-May/msg00031.html Warning is printed with 80, 85, 90, 95, 100% In release bugfix - moving to ON_QA. Tested with lvm2-2.02.171-2.el7 and it works well. I can see the messages below as the pool is being used. WARNING: Thin pool testvg-pool3-tpool data is now 81.00% full. WARNING: Thin pool testvg-pool3-tpool data is now 91.00% full. WARNING: Thin pool testvg-pool3-tpool data is now 96.00% full. In release bug. Closing as fixed. |