Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Installing RHVH with Anaconda 21.48.22.121-1(the 7.4 version), the free space in volume group is larger than the one with Anaconda 7.3, no matter choosing auto partitioning or custom partitioning on GUI, or setting autopart in kickstart file.
To take auto partitioning as an example, the free space in volume group with Anaconda 7.4 is like:
[root@dhcp-10-111 ~]# vgs
VG #PV #LV #SN Attr VSize VFree
rhvh_dhcp-10-111 1 10 0 wz--n- 231.88g <45.48g
[root@dhcp-10-111 ~]# lvs -a
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
home rhvh_dhcp-10-111 Vwi-aotz-- 1.00g pool00 4.79
[lvol0_pmspare] rhvh_dhcp-10-111 ewi------- 96.00m
pool00 rhvh_dhcp-10-111 twi-aotz-- <181.44g 3.55 0.42
[pool00_tdata] rhvh_dhcp-10-111 Twi-ao---- <181.44g
[pool00_tmeta] rhvh_dhcp-10-111 ewi-ao---- 1.00g
rhvh-4.1-0.20170714.0 rhvh_dhcp-10-111 Vwi---tz-k <154.44g pool00 root
rhvh-4.1-0.20170714.0+1 rhvh_dhcp-10-111 Vwi-aotz-- <154.44g pool00 rhvh-4.1-0.20170714.0 2.61
root rhvh_dhcp-10-111 Vwi-a-tz-- <154.44g pool00 2.73
swap rhvh_dhcp-10-111 -wi-ao---- <3.88g
tmp rhvh_dhcp-10-111 Vwi-aotz-- 1.00g pool00 4.81
var rhvh_dhcp-10-111 Vwi-aotz-- 15.00g pool00 2.87
var_log rhvh_dhcp-10-111 Vwi-aotz-- 8.00g pool00 3.26
var_log_audit rhvh_dhcp-10-111 Vwi-aotz-- 2.00g pool00 4.77
[root@dhcp-10-111 ~]# imgbase w
2017-07-18 09:50:38,878 [INFO] You are on rhvh-4.1-0.20170714.0+1
The free space in volume group with Anaconda 7.3 is like:
[root@dhcp-10-111 ~]# vgs
VG #PV #LV #SN Attr VSize VFree
rhvh_dhcp-10-111 1 10 0 wz--n- 231.88g 14.90g
[root@dhcp-10-111 ~]# imgbase w
2017-07-20 16:17:53,667 [INFO] You are on rhvh-4.1-0.20170706.0+1
[root@dhcp-10-111 ~]# lvs -a
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
home rhvh_dhcp-10-111 Vwi-aotz-- 1.00g pool00 4.83
[lvol0_pmspare] rhvh_dhcp-10-111 ewi------- 108.00m
pool00 rhvh_dhcp-10-111 twi-aotz-- 212.00g 2.11 0.18
[pool00_tdata] rhvh_dhcp-10-111 Twi-ao---- 212.00g
[pool00_tmeta] rhvh_dhcp-10-111 ewi-ao---- 1.00g
rhvh-4.1-0.20170706.0 rhvh_dhcp-10-111 Vwi---tz-k 197.00g pool00 root
rhvh-4.1-0.20170706.0+1 rhvh_dhcp-10-111 Vwi-aotz-- 197.00g pool00 rhvh-4.1-0.20170706.0 1.45
root rhvh_dhcp-10-111 Vwi-a-tz-- 197.00g pool00 1.55
swap rhvh_dhcp-10-111 -wi-ao---- 3.88g
tmp rhvh_dhcp-10-111 Vwi-aotz-- 2.00g pool00 4.81
var rhvh_dhcp-10-111 Vwi-aotz-- 15.00g pool00 3.31
var-log rhvh_dhcp-10-111 Vwi-aotz-- 8.00g pool00 3.23
var-log-audit rhvh_dhcp-10-111 Vwi-aotz-- 2.00g pool00 4.12
Obviously, 45.48g is much larger than 14.90g.
As per Bug 1131247, 20% of volume group size will be reserved when choosing auto partitioning. But the free space calculation algorithm in Anaconda 7.3 seems more reasonable, for RHVH suggests customers to use auto partitioning, 20% free space seems too big.
Version-Release number of selected component (if applicable):
7.4 build:
redhat-virtualization-host-4.1-20170714.1
RHVH-4.1-20170718.2-RHVH-x86_64-dvd1.iso
7.3 build:
redhat-virtualization-host-4.1-20170706.0
RHVH-4.1-20170706.1-RHVH-x86_64-dvd1.iso
How reproducible:
100%
Steps to Reproduce:
1. Install 7.4 build via Anaconda GUI, choose auto partitioning
2. After installation finished, log into RHVH, run 'vgs' to check VFree
3. Install 7.3 build via Anaconda GUI on the same machine with step1 , choose auto partitioning
4. After installation finished, log into RHVH, run 'vgs' to check VFree
Actual results:
1. VFree is about 20% of Vsize in 7.4 build
2. VFree in 7.4 build is much larger than in 7.3
Expected results:
1. VFree in 7.4 could be the same with in 7.3.
Additional info:
If you want to control the amount of space reserved for thin pool metadata you will have to use kickstart to specify a manual storage configuration. This is not configurable when using automatic partitioning.
Reassigning to vpodzime in case he has further comments before we close this.
Is there a reason we wouldn't be able to set this from our installclass?
Comment 4Vratislav Podzimek
2017-08-08 07:43:55 UTC
(In reply to Ryan Barry from comment #3)
> Is there a reason we wouldn't be able to set this from our installclass?
You mean how much percent of the VG is reserved?
I think we can close this bug now. The reasons are:
First, after Bug 1131247 was fixed, users can specify the vg free space manually by using --reserved-percent/--reserved-space option if they think 20% is too large. (On RHVH 4.4, reserved-percent doesn't work, it's tracked by bug 1783946)
Second, we haven't got any complaints from customers till now that the default vg free space of auto part is unacceptable.
Comment 10Sandro Bonazzola
2020-03-26 07:17:16 UTC
(In reply to Qin Yuan from comment #9)
> I think we can close this bug now. The reasons are:
>
> First, after Bug 1131247 was fixed, users can specify the vg free space
> manually by using --reserved-percent/--reserved-space option if they think
> 20% is too large. (On RHVH 4.4, reserved-percent doesn't work, it's tracked
> by bug 1783946)
> Second, we haven't got any complaints from customers till now that the
> default vg free space of auto part is unacceptable.
Thanks, closing this for RHEL 8.2 / RHV 4.4