Bug 1336367
Summary: | [z-stream clone - 3.6.7] Growing backing file length in qcow2 header causes 'Backing file name too long' error. | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
Component: | vdsm | Assignee: | Adam Litke <alitke> |
Status: | CLOSED ERRATA | QA Contact: | Elad <ebenahar> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.6.5 | CC: | alitke, amureini, bazulay, eblake, gveitmic, gwatson, jsuchane, lsurette, mkalinin, nsoffer, pkrempa, ratamir, srevivo, stirabos, tnisan, ycui, ykaul, ylavi |
Target Milestone: | ovirt-3.6.7 | Keywords: | ZStream |
Target Release: | 3.6.7 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, when creating snapshots the backing volume reference included an image directory component. Each time a snapshot was merged, the image directory component of the backing volume reference was duplicated until the backing volume reference became too long. In this state the image could not be used. Now, since all volumes of an image always reside in the same directory, the image directory component has been removed from new backing volume references. Now the backing volume references do not grow in length after snapshots are merged.
|
Story Points: | --- |
Clone Of: | 1333627 | Environment: | |
Last Closed: | 2016-06-29 16:22:42 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: | 1333627 | ||
Bug Blocks: |
Comment 2
Elad
2016-06-13 11:47:21 UTC
Correction: the backing file (f42045f2-d5f7-4c7d-85e7-bc967f6f1c78) is snapshot B as expected. Clonned doctext from the 4.0 bug 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. https://access.redhat.com/errata/RHBA-2016:1365 |