Create partition

[burn3r10]

Hello,

Trying to create a simple partition on the drive that is not the WHOLE drive. It looks like proxmox decided not to add this to the GUI so it's been a nightmare to complete. So how do you create a simple LVM-thin partition that is only 500G of the 4Tb drive?

I've also had to sign up TWICE for this forum because it decided not to work the first time.

 

[burn3r10]

On windows I would've been done in 2 minutes... via gui.

 

[BobhWasatch]

On windows I would've been done in 2 minutes... via gui.

So do that and use Hyper-V as the hypervisor.

 

[burn3r10]

So do that and use Hyper-V as the hypervisor.

Because that's not what I'm trying to do? I spent over an hour trying to create a partition and volume the way I want. So appreciate the not help?

 

[BobhWasatch]

Because that's not what I'm trying to do?

Why did you bring it up then?

As far as I know the GUI only supports creating an LVM-thin on a whole disk. It isn't exactly an enterprise use-case to have other things on the same disk as your VM's, while it is one to have entire disks dedicated to VM storage. That being said, it can be done from the command line. Assuming the partition is "/dev/sdb1" and you will name the volume group "vg0" and the thin pool "data" takes up the whole volume group it would be something like this:

pvcreate /dev/sdb1
vgcreate vg0 /dev/sdb1
lvcreate -l 100%FREE --thinpool data vg0

 

[burn3r10]

Because it's been incredibly frustrating to complete what I perceive as a simple task. I just want to set aside a portion of it for containers to move between nodes with two different storage sizes. Seeing as one mode is 500G and the other 4T, I don't wanna create a 4T partition. Since as I learned both nodes need to have storage named the same way to migrate containers.

 

[BobhWasatch]

I don't run a cluster but AFAIK the storages don't have to be the same size on all nodes for migration to work. You just need to have sufficient space on the target.

 

[burn3r10]

No. That was just to ensure that I don't cut into it's storage so the containers can migrate over when needed and I don't accidentally allocate the space to anything else since I'll be running VMs and doing NFS on the main host as well.