From 2ea5c4a5ea0499e5359e5e6632907e72aac7fdba Mon Sep 17 00:00:00 2001 From: Thomas Lamprecht Date: Wed, 11 Jan 2017 10:37:48 +0100 Subject: [PATCH 1/1] pvecm: explain need of storage separation on node separation better VMID conflict are not the main problem, and some users could think that they can handle VMID conflict them self and thus do not separate the storages. Therefore mention the locking over cluster boundary problem too. Signed-off-by: Thomas Lamprecht --- pvecm.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/pvecm.adoc b/pvecm.adoc index 968df87..21ceb1e 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -275,7 +275,8 @@ You can also separate a node from a cluster without reinstalling it from scratch. But after removing the node from the cluster it will still have access to the shared storages! This must be resolved before you start removing the node from the cluster. A {pve} cluster cannot share the exact same -storage with another cluster, as it leads to VMID conflicts. +storage with another cluster, as storage locking doesn't work over cluster +boundary. Further, it may also lead to VMID conflicts. Its suggested that you create a new storage where only the node which you want to separate has access. This can be an new export on your NFS or a new Ceph -- 2.39.2