proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-04-29 23:17:37 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

pvecm: explain need of storage separation on node separation better

Browse Source 
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 <t.lamprecht@proxmox.com>
This commit is contained in:
Thomas Lamprecht 2017-01-11 10:37:48 +01:00 committed by Dietmar Maurer
parent 9e73d83160
commit 2ea5c4a5ea
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
pvecm.adoc
View File

@ -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