Trying to create an additional disk but a bit lost by the term extents.
Here is what I did.
sgdisk -N 1 /dev/sdb
Creating new GPT entries.
The operation has completed successfully.
pvcreate --metadatasize 250k -y -ff /dev/sdb1
Physical volume "/dev/sdb1" successfully created.
vgcreate vmdata /dev/sdb1
Volume group "vmdata" successfully created
vgdisplay
--- Volume group ---
VG Name vmdata
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 1
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 0
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 976.95 GiB
PE Size 4.00 MiB
Total PE 250100
Alloc PE / Size 0 / 0
Free PE / Size 250100 / 976.95 GiB
VG UUID H2rOn5-2h0o-8q8c-Qi3t-YoMO-aOXF-9I5804
lvcreate -L 976.95G -n ssd-data vmdata
Rounding up size to full physical extent 976.95 GiB
Logical volume "ssd-data" created.
lvconvert --type thin-pool vmdata/ssd-data
WARNING: Converting logical volume vmdata/ssd-data to thin pool's data volume with metadata wiping.
THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.)
Do you really want to convert vmdata/ssd-data? [y/n]: y
Volume group "vmdata" has insufficient free space (0 extents): 31 required.
Should I leave some space available. How much? How does it work?
Here is what I did.
sgdisk -N 1 /dev/sdb
Creating new GPT entries.
The operation has completed successfully.
pvcreate --metadatasize 250k -y -ff /dev/sdb1
Physical volume "/dev/sdb1" successfully created.
vgcreate vmdata /dev/sdb1
Volume group "vmdata" successfully created
vgdisplay
--- Volume group ---
VG Name vmdata
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 1
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 0
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 976.95 GiB
PE Size 4.00 MiB
Total PE 250100
Alloc PE / Size 0 / 0
Free PE / Size 250100 / 976.95 GiB
VG UUID H2rOn5-2h0o-8q8c-Qi3t-YoMO-aOXF-9I5804
lvcreate -L 976.95G -n ssd-data vmdata
Rounding up size to full physical extent 976.95 GiB
Logical volume "ssd-data" created.
lvconvert --type thin-pool vmdata/ssd-data
WARNING: Converting logical volume vmdata/ssd-data to thin pool's data volume with metadata wiping.
THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.)
Do you really want to convert vmdata/ssd-data? [y/n]: y
Volume group "vmdata" has insufficient free space (0 extents): 31 required.
Should I leave some space available. How much? How does it work?