Bug 1470931 - [RFE] Provide a way to safely run LVM commands
[RFE] Provide a way to safely run LVM commands
Status: NEW
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm (Show other bugs)
4.1.3
x86_64 Linux
medium Severity high
: ovirt-4.3.0
: ---
Assigned To: Dan Kenigsberg
Elad
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-13 23:49 EDT by Germano Veit Michel
Modified: 2018-03-05 10:07 EST (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Germano Veit Michel 2017-07-13 23:49:16 EDT
Description of problem:

We have recently learned that running lvm commands without proper parameters with  lvmetad running can ruin a Storage Domain. We also know that to run LVM commands safely, the Storage Domain must be in maintenance mode in order to prevent them from clashing with SPM lvm commands.

However, maintenance mode is hardly accepted by customers as it puts all the VMs of the Storage Domain down. This is undesirable, correcting a single failure (removing an orphan LV or changing a tag) should not require the entire Storage Domain to be shutdown, these are often production VMs.

What is requested here is some sort of:
vdsm-client run-lvm-command <my lvm command here>

vdsm would then take care of running this command, adding the required configuration such as lvmetad=0 and also ensuring no other LVM command runs in parallel and also the current host is still the SPM at the time the command is issued.

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