Extending a current volume or creating a new one when adding a drive?

[Mullasci]

Context:
I have PVE 8.3.0 running on a relatively small system with a 1TB NVMe (WD Black SN850X) and 32GB of DDR4 memory.
So far I have no issues, but if the thin-provisioned disks of the current VMs will expand to their maximum size I will run into problems because they are over-provisioned (~1.5TB in total if full expanded)
I have acquired a second 2TB NVMe that would be able to support all the VMs disks at their maximum size.
The new NVMe is DRAM-less thus lower performance that the first one.
I have a 64GB of swap partition in the original NVMe that is intensively used (yes I had to over-provision the memory too to get an OpenShift cluster running to perform some checks)

The questions are:
Which criteria should guide the decision between
a) extend the current LVM-Thin with the 2TB of the new drive or
b) create a new LVM-Thin and move the VM's disks there?
What are the tradeoffs of the two options?
There are other alternatives I'm not considering but I should add to the list?

 

[bbgeek17]

b) create a new LVM-Thin and move the VM's disks there?

You should go this route

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Mullasci]

You should go this route

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

The process went smooth and almost without surprises.
Except for the fact that all the disks apparently became thick provisioned in the process and I have 1.45TB consumed in the new storage instead of the 245GB I had in the original local-lvm.
Did I miss something when I created the new space?
It might be due to the fact I moved the disks with the VMs running?
Aside from the disk usage, which in itself is not an issue, there are other side effects?
Below is the creation log:

Physical volume "/dev/nvme0n1" successfully created.
Volume group "dataslow" successfully created
Reducing pool metadata size 16.00 GiB to maximum usable size <15.88 GiB.
Thin pool volume with chunk size 64.00 KiB can address at most <15.88 TiB of data.
Logical volume "dataslow" created.
TASK OK

{UPDATE}
I found the answer to my question about the disk expansion in an old thread: https://forum.proxmox.com/threads/v...fter-migrating-it-to-lvm-thin-storage.142070/