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.

Created attachment 459059 [details]
Inflated VMs

Description of problem:
When using sparse LV - image keeps inflating beyond virtual size until there is no more room in the storage

In the attached, screenshot the inflated VMs Win7-1 and Win7-2 are derived from the same template as Win7-serv - but only these two have inflated.

The difference: 
Both inflating VMs are running on a non SPM host, while the reasonable size VM is on the SPM host
Both inflating VMs are virtual desktops while the other is a virtual server.


Version-Release number of selected component (if applicable):
IC41
VDSM 4.9.0.22

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Attached: Screen shot, Log collector

Created attachment 459062 [details]
Log Collector output

please attach qemu-img info output on the relevant LVs

The crux of the issue is that libvirt does not refresh the reported physical size after lvextend:

# virsh domblkinfo 20c0d64c-d706-439a-a39b-9ced382004f0 /rhev/data-center/2c765f7a-2cf1-4025-a107-2c76d44af6a9/5235507a-a6c7-4ec1-a34e-4f7f754a1230/images/4a79ca7d-371d-4a9b-8f8d-a0010b005f26/8e714d9f-b83c-47b5-9d70-8dbae7f8ea13
Capacity:       16106127360
Allocation:     11483217408
Physical:       4294967296

[root@vm-18-16 ~]# lvs |grep 8e714d9f-b83c-47b5-9d70-8dbae7f8ea13 
  8e714d9f-b83c-47b5-9d70-8dbae7f8ea13 5235507a-a6c7-4ec1-a34e-4f7f754a1230 -wi-ao 187.00g


to solve this quickly and efficiently, vdsm will use its own sense of the physical size when emulating the high write event.

*** Bug 657830 has been marked as a duplicate of this bug. ***

http://git.engineering.redhat.com/?p=users/bazulay/vdsm.git;a=commitdiff;h=7b25c534570410b9e139bd77def06536ceb9e0b2

Verified using rhel6 host with vdsm-4.9-29.el6.x86_64, created desktop machine from template on iSCSI storage based on LVs.