I have (or well, had) 3 nodes running in a cluster.
Two of these nodes only have one SATA port and just use the default LVM configuration. (one with a 256GB SSD and the other with a 512GB SSD)
The other node has a second SATA port so I figured "why not, let's use it". (this one has a 128GB SSD and a 256GB HDD)
Turns out I'm unable to migrate containers to another node if the storage name doesn't match, so for this last node I kept having to move the disk to
So I decided to rebuild the node with two disks. After painstakingly moving disks around and migrating it, decommissioned from cluster with
The problem:
As I rebuild this node, i realize that each LVM-thin storage type can only have a single VG name, as seen in
This is a problem for this two-drive node, because Proxmox will set up the
So now I'm at a catch-22: I cannot migrate VMs because the storage name doesn't match, and I cannot make the storage name match because Proxmox installer will only ever use the name
So how can I make migration work without having to move the disk from the HDD to SSD every time I want to take this node offline?
Two of these nodes only have one SATA port and just use the default LVM configuration. (one with a 256GB SSD and the other with a 512GB SSD)
The other node has a second SATA port so I figured "why not, let's use it". (this one has a 128GB SSD and a 256GB HDD)
Turns out I'm unable to migrate containers to another node if the storage name doesn't match, so for this last node I kept having to move the disk to
local-lvm to be able to THEN migrate to any of the other nodes. It would be nice if I could select a storage for the disks to migrate to but I guess I don't live in an ideal world.So I decided to rebuild the node with two disks. After painstakingly moving disks around and migrating it, decommissioned from cluster with
pvecm delnode.The problem:
As I rebuild this node, i realize that each LVM-thin storage type can only have a single VG name, as seen in
storage.cfg:
Code:
root@lhs-pve02:~# cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content iso,backup,vztmpl
lvmthin: local-lvm
thinpool data
vgname pve
content images,rootdir
nodes lhs-pve04,lhs-pve02
nfs: pvebackup
export /mnt/user/pvebackup
path /mnt/pve/pvebackup
server 172.20.0.5
content backup
prune-backups keep-all=1This is a problem for this two-drive node, because Proxmox will set up the
pve VG by default during installation, and that means I can't create the pve VG on the HDD since the rootfs is on the SSD and I want local-lvm on the HDD.So now I'm at a catch-22: I cannot migrate VMs because the storage name doesn't match, and I cannot make the storage name match because Proxmox installer will only ever use the name
pve for its initial install, meaning I cannot create local-lvm on the second drive.So how can I make migration work without having to move the disk from the HDD to SSD every time I want to take this node offline?