Bug 1278959

Summary: lvm2: thin-pool: Grow thin pool by smaller than desired free space
Product: Red Hat Enterprise Linux 7 Reporter: Vivek Goyal <vgoyal>
Component: lvm2Assignee: Zdenek Kabelac <zkabelac>
lvm2 sub component: Thin Provisioning QA Contact: cluster-qe <cluster-qe>
Status: CLOSED WONTFIX Docs Contact:
Severity: unspecified    
Priority: unspecified CC: agk, heinzm, jbrassow, msnitzer, prajnoha, thornber, zkabelac
Version: 7.3   
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: 2020-12-15 07:38:15 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 Vivek Goyal 2015-11-06 20:59:42 UTC 
Description of problem:

Right now if a user has configured thin pool to be grown by 20%, that means
we calculate the 20% of existing thin pool size and grow pool by that amount. What if desire free space is not available in volume group. In that case thin pool extension fails. 

Change the logic in such a way so that if lesser amount of free space is
available than desired space, then thin pool can be grown by smaller
amount of free space.

For example, say I have a thin pool of size 50G, and pool grows by 20%,
then 10GB free space is required in volume group. But if only 8GB free space
is availabe, pool should still grow by 8GB instead of failing to grow.
 
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 RHEL Program Management 2020-12-15 07:38:15 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.