[pve-devel] Storage::Plugin::deactivate_volume not executed, when VM does shutdown

Dietmar Maurer dietmar at proxmox.com
Sun Dec 11 15:49:10 CET 2016


>  > Why? There is no real need to deactivate a volume, unless you move the VM
>  > to another node.
> I already told you why:
>    For a DRBD8 plugin, which I want to write, it is essential to switch the

IMHO DRBD8 is old and replaced by DRBD9. Linbit will provide a DRBD9 driver
in future ....

But yes, that drbdmanage package has kind of a non-free License.

>    volume back to secondary after using it. Otherwise it can't be used on the
>    other machine and you need manual intervention to solve this issue.

First, we call deactivate if you migrate a VM to another node.
For HA, you need to fence the node before you start it on another node,
so there is no need to deactivate the volume at VM stop time.

Besides, DRBD9 has built in support for auto-promotion, so it would 
be preferable to use that mode (strongly suggested by Linbit to avoid
split brain).

https://www.drbd.org/en/doc/users-guide-90/s-automatic-promotion

So if the VM stops, all used DRBD9 resources changes back to 
secondary - automatically!




More information about the pve-devel mailing list