i have used the nice tutorial at https://aaronlauterer.com/blog/2021/proxmox-ve-migrate-to-smaller-root-disks/. at several times to migrate proxmox host to smaller zfs disk. nice tutorial !
now i need to do that with a proxmox host being part of a cluster.
do i need to take any additional precaution when bringing up the node after clone , as it moves backward in time, because it does contain an older copy of the cluster config.db , i.e. on restart , the node has an older copy of config.db ?
will it rejoin/get active without problems or can this caus corruption?
maybe @aaron may know and want's to add a note to the blog post ?
now i need to do that with a proxmox host being part of a cluster.
do i need to take any additional precaution when bringing up the node after clone , as it moves backward in time, because it does contain an older copy of the cluster config.db , i.e. on restart , the node has an older copy of config.db ?
will it rejoin/get active without problems or can this caus corruption?
maybe @aaron may know and want's to add a note to the blog post ?
Last edited:
) before being allowed to handle ongoing changes. since any node can only write to /etc/pve after having synced up and while being part of the quorate partition, the only way to mess this basic property up is by splitting the cluster and then making both parts quorate by modifying the quorum settings (e.g., setting expected votes or similar shenanigans).