[pve-devel] [PATCH qemu-server 1/2] deactivate new volumes after clone to other node

Wolfgang Bumiller w.bumiller at proxmox.com
Tue Jul 26 11:20:40 CEST 2016


applied both patches

On Wed, Jul 13, 2016 at 12:44:12PM +0200, Fabian Grünbichler wrote:
> this might otherwise lead to volumes activated on the
> source and target node, which is problematic for at least
> LVM and Ceph.
> ---
>  PVE/API2/Qemu.pm | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/PVE/API2/Qemu.pm b/PVE/API2/Qemu.pm
> index 7337887..83611a6 100644
> --- a/PVE/API2/Qemu.pm
> +++ b/PVE/API2/Qemu.pm
> @@ -2391,6 +2391,7 @@ __PACKAGE__->register_method({
>                      if ($target) {
>  			# always deactivate volumes - avoid lvm LVs to be active on several nodes
>  			PVE::Storage::deactivate_volumes($storecfg, $vollist, $snapname) if !$running;
> +			PVE::Storage::deactivate_volumes($storecfg, $newvollist);
>  
>  			my $newconffile = PVE::QemuConfig->config_file($newid, $target);
>  			die "Failed to move config to node '$target' - rename failed: $!\n"
> -- 
> 2.1.4
> 
> 
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> 



More information about the pve-devel mailing list