Bug 1031833 - wrong actual disk size
Summary: wrong actual disk size
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.3.3
Assignee: Tal Nisan
QA Contact: Aharon Canan
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-18 22:27 UTC by Arik
Modified: 2016-02-10 16:43 UTC (History)
8 users (show)

Fixed In Version: ovirt-3.3.3-beta1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-14 09:56:59 UTC
oVirt Team: Storage

Attachments (Terms of Use)
disk with virtual size = 20 gb and actual size = 6200 gb (186.81 KB, image/png)
2013-11-18 22:27 UTC, Arik 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 21490 0 None None None Never

Description Arik 2013-11-18 22:27:34 UTC 
Created attachment 825831 [details]
disk with virtual size = 20 gb and actual size = 6200 gb

Description of problem:
it seems that there is a bug when we determine the actual disk size that cause it to be huge after running the VM 

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


How reproducible:
always happened to me when I created VMs from the same template of fedora 19

Steps to Reproduce:
1. create template from a VM installed with fedora 19
2. create a VM based on that template
3. run the VM

Actual results:
after the VM starts, the actual size of the disk is huge

Expected results:
the actual size of disk should be less than the virtual size

Additional info:
before running the VM the actual size of my VM's disk was +-3 gb and after running the VM it was changed to +-6200 gb. a screen shot is attached
Comment 1 Allon Mureinik 2013-11-20 14:26:39 UTC 
Arik, you did not specify which version this happened on.
Can you provide this info (or better yet, a commit hash)?
Comment 2 Allon Mureinik 2013-11-20 14:27:52 UTC 
Arik, you did not specify which version this happened on.
Can you provide this info (or better yet, a commit hash)?
Comment 3 Arik 2013-11-25 13:12:46 UTC 
It was +-the latest at the time I opened the bug
Comment 4 Tal Nisan 2013-11-25 16:13:08 UTC 
Sergey, if I recall correctly you were working on a related issue, can you please check if it's a dup?
Comment 5 Sandro Bonazzola 2014-02-14 09:56:59 UTC 
Closing as 3.3.3 has been released.
Note You need to log in before you can comment on or make changes to this bug.