Bug 1395383 - [RFE]Add a way to run qemu-img check on RHV VM disks
Summary: [RFE]Add a way to run qemu-img check on RHV VM disks
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.0.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Avihai
URL:
Whiteboard:
Depends On:
Blocks: 902971
TreeView+ depends on / blocked
 
Reported: 2016-11-15 21:00 UTC by Marina Kalinin
Modified: 2020-04-01 14:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-01 14:46:16 UTC
oVirt Team: Storage
Target Upstream Version:


Attachments (Terms of Use)

Description Marina Kalinin 2016-11-15 21:00:58 UTC
Would be nice to have the option to perform `qemu-img check` on RHV VM disks.

Where/How:
First step: it can be vdsm verb available through vdsClient.
Next step:  it can be a button in UI, next to each disk, to run disk check.

Version-Release number of selected component (if applicable):
It is not available as of 4.0.5.

Why do we need this?
It is nice to have when working on issues with snapshots and potential data corruption. Would make it easier to debug and report the problem.

Comment 1 Yaniv Lavi 2017-11-26 13:52:01 UTC
Any thoughts on this?
Maybe we can provide this as part of log collection run?

Comment 2 Allon Mureinik 2017-11-26 14:53:57 UTC
(In reply to Yaniv Lavi from comment #1)
> Any thoughts on this?
> Maybe we can provide this as part of log collection run?
Definitely not - you need to orchestrate preparing and tearing down the image and running things (like VMs ;-)) against it.

Marina's suggestion sounds like the right way to go.

Comment 3 Michal Skrivanek 2020-03-18 15:45:12 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:50:09 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:46:16 UTC
ok, closing. Please reopen if still relevant/you want to work on it.

Comment 6 Michal Skrivanek 2020-04-01 14:50:18 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.