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:
When the volume format is raw what the disk capacity seen by the guest is the actual size of the file/device therefore if the requested size doesn't match the real size (eg: extends granularity in LVM) we need to update the size value so that the metadata reflects the correct state.

Version-Release number of selected component (if applicable):
vdsm-4.9.6-38.0.el6_3

How reproducible:
100%

Steps to Reproduce:
1. create a raw preallocated volume on iscsi using a size that is not a multiple of the lvm pe (128Mb by default), eg: 10Mb (using the restapi, the ui prevents it).
2. verify that the created lv is indeed using the pe granularity (128Mb)
3. getVolumeSize reports a capacity of 10Mb (while the guest would see a 128Mb disk).
  
Actual results:
The metadata doesn't reflect what the guest actually sees in terms of disk capacity.

Expected results:
The metadata should reflect what the guest actually sees in terms of disk capacity.

commit 097acc6eab78a54e01d920b11621f57f908fd63b
Author: Federico Simoncelli <fsimonce>
Date:   Wed Oct 17 08:07:57 2012 -0400

    volume: save the correct size during creation
    
http://gerrit.ovirt.org/#/c/8629/

Verified vdsm-4.9.6-41.0.el6_3.x86_64

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-1508.html