Bug 1032106 - _highWrite should not extend a drive if the highest allocated extent is outside the capacity of the volume.
Summary: _highWrite should not extend a drive if the highest allocated extent is outsi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.2.0
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: ---
: 3.2.5
Assignee: Federico Simoncelli
QA Contact: Aharon Canan
URL:
Whiteboard: storage
Depends On: 998443
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-19 14:58 UTC by rhev-integ
Modified: 2018-12-03 20:45 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
QEMU sometimes returned a value for the highest allocated extent of a volume that was greater than the capacity of the qcow2 volume. In such a case VDSM attempted to extend the volume with every run of _highWrite. It did not ensure that the highest allocated extent was within the capacity of the volume before proceeding. Both _highWrite and _onAbnormalStop now share the same logic about the volume extension.
Clone Of: 998443
Environment:
Last Closed: 2013-12-18 13:58:43 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 429853 0 None None None Never
Red Hat Product Errata RHBA-2013:1832 0 normal SHIPPED_LIVE rhev 3.2.5 - vdsm bug fix update 2013-12-18 18:56:17 UTC
oVirt gerrit 21150 0 None None None Never
oVirt gerrit 21382 0 None None None Never
oVirt gerrit 21383 0 None None None Never

Comment 2 Charlie 2013-11-29 04:10:07 UTC 
Hi all need some information on this to write the doc text (if needed).

Thanks
Comment 3 Aharon Canan 2013-12-04 11:51:07 UTC 
verified using sf22 (following comment #14 in the original bug https://bugzilla.redhat.com/show_bug.cgi?id=998443#c14) with Lee's help.
Comment 4 Federico Simoncelli 2013-12-14 15:31:04 UTC 
Doc Text is correct.
Comment 6 errata-xmlrpc 2013-12-18 13:58:43 UTC 
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/RHBA-2013-1832.html
Note You need to log in before you can comment on or make changes to this bug.