Bug 1032106
| Summary: | _highWrite should not extend a drive if the highest allocated extent is outside the capacity of the volume. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | vdsm | Assignee: | Federico Simoncelli <fsimonce> |
| Status: | CLOSED ERRATA | QA Contact: | Aharon Canan <acanan> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 3.2.0 | CC: | abaron, amureini, bazulay, cboyle, eedri, fsimonce, hateya, iheim, lpeer, pzhukov, scohen, sgotliv, yeylon |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | 3.2.5 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | storage | ||
| 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.
|
Story Points: | --- |
| Clone Of: | 998443 | Environment: | |
| Last Closed: | 2013-12-18 13:58:43 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 998443 | ||
| Bug Blocks: | |||
|
Comment 2
Charlie
2013-11-29 04:10: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. Doc Text is correct. 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 |