Bug 1551684 - [CodeChange][Tracking] Map and remove vdsm flows that needlessly prepare the entire chain
Summary: [CodeChange][Tracking] Map and remove vdsm flows that needlessly prepare the ...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.20.19
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Dan Kenigsberg
QA Contact: Avihai
URL:
Whiteboard:
Depends On: 1395941
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-05 17:43 UTC by Allon Mureinik
Modified: 2020-04-01 14:51 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-04-01 14:47:46 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.3+


Attachments (Terms of Use)

Description Allon Mureinik 2018-03-05 17:43:25 UTC
Description of problem:
qemu-img-[[rh]ev]-2.10 provided the ability to perform "unsafe" operations on the leaf of a qcow2 chain, without preparing the entire backing chain (see bug 1213786) for details.

This BZ is a tracker for mapping out places where vdsm needlessly prepares the entire chain and fixing them so they prepare the minimal number of volumes, if at all.
Fixing these would both improve performance and reduce the risk of leaving "leftover" prepared volumes they may later cause problems.

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

An initial list of flows to consider:
- Creating a snapshot (already handled by bug 1395941).
- Creating a thin VM/pool on top of a snapshot (possibly handled by the previous item)
- Merging a snapshot (only the two volumes merged should be activated, at least in theory)
- Amending qcow compat level
- Extending the size of a disk
- getVolumeInfo
-

Comment 2 Sandro Bonazzola 2019-01-28 09:37:02 UTC
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 3 Michal Skrivanek 2020-03-18 15:46:43 UTC
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 4 Michal Skrivanek 2020-03-18 15:51:29 UTC
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 5 Michal Skrivanek 2020-04-01 14:47:46 UTC
ok, closing. Please reopen if still relevant/you want to work on it.

Comment 6 Michal Skrivanek 2020-04-01 14:51:11 UTC
ok, closing. Please reopen if still relevant/you want to work on it.


Note You need to log in before you can comment on or make changes to this bug.