Bug 651335

Summary: When using sparse LV - image keeps inflating beyond virtual size until there is no more room in the storage
Product: Red Hat Enterprise Linux 6 Reporter: Simon Grinberg <sgrinber>
Component: vdsmAssignee: Dan Kenigsberg <danken>
Status: CLOSED CURRENTRELEASE QA Contact: Jakub Libosvar <jlibosva>
Severity: urgent Docs Contact:
Priority: low    
Version: 6.0CC: abaron, acathrow, bazulay, danken, iheim, mbabayev, pstehlik, Rhev-m-bugs, ykaul
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: vdsm-4.9-27.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-19 15:04:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 651803    
Bug Blocks:    
Attachments:
Description Flags
Inflated VMs
none
Log Collector output none

Description Simon Grinberg 2010-11-09 09:58:32 UTC
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

Comment 1 Simon Grinberg 2010-11-09 10:02:45 UTC
Created attachment 459062 [details]
Log Collector output

Comment 4 Ayal Baron 2010-11-09 10:35:06 UTC
please attach qemu-img info output on the relevant LVs

Comment 5 Dan Kenigsberg 2010-11-10 10:00:12 UTC
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.

Comment 6 Barak 2010-11-28 13:07:34 UTC
*** Bug 657830 has been marked as a duplicate of this bug. ***

Comment 8 Jakub Libosvar 2010-12-10 13:47:04 UTC
Verified using rhel6 host with vdsm-4.9-29.el6.x86_64, created desktop machine from template on iSCSI storage based on LVs.