Adding LVM2 Volume Groups Shows 0% Available and 0% Free

Thu, 12 Aug 2021 03:47:58 GMT

Hi,

You can visit create vps page after adding storage and then it would sync it instantly.

Adding LVM2 Volume Groups Shows 0% Available and 0% Free

Wed, 11 Aug 2021 20:04:20 GMT

I just fixed this by logging out of my admin user and logging back in as root, setting up the storages again, logging out, and logging in. I guess the web interface won't refresh the storage appropriately until then. Is this a bug?

Wed, 11 Aug 2021 19:47:50 GMT

I created two volume groups vg_ssd0 and vg_hdd0 and both do not contain any logical volumes (Running lvs command results in no associated LV's). Docs say to add the storage and give the path to the VG as "/dev/vg_ssd0" or "/dev/vg_hdd0". I do this and get Size = 0 G and Free = 0 G.

When I do "ls /dev/ | grep vg" I do not see the devices "/dev/vg_ssd0" or "/dev/vg_hdd0". I only see those device show up if I actually create logical volumes with "lvcreate" on each volume group. For example, creating LV "lv_ssd0" and "lv_hdd0" I do see "/dev/vg_ssd0/lv_ssd0" and "/dev/vg_hdd0/lv_hdd0".

Here is output from pvs, vgs, lvs:

Code
rrojas@rrojas-ubuntuserver:~$ sudo pvs

  PV         VG      Fmt  Attr PSize    PFree

  /dev/sdb3  vghost  lvm2 a--  <200.00g      0

  /dev/sdb4  vg_ssd0 lvm2 a--   749.36g 749.36g

  /dev/sdc   vg_hdd0 lvm2 a--   931.51g 931.51g

  /dev/sdd   vg_hdd0 lvm2 a--   931.51g 931.51g

rrojas@rrojas-ubuntuserver:~$ sudo vgs

  VG      #PV #LV #SN Attr   VSize    VFree

  vg_hdd0   2   0   0 wz--n-   <1.82t  <1.82t

  vg_ssd0   1   0   0 wz--n-  749.36g 749.36g

  vghost    1   1   0 wz--n- <200.00g      0

rrojas@rrojas-ubuntuserver:~$ sudo lvs

  LV   VG     Attr       LSize    Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert

  lv-0 vghost -wi-ao---- <200.00g

As a note, vghost is a dedicated volume group for the hosting OS install with a single logical volume. This will not be used for VPS storage. Notice that vghost and vg_ssd0 come from the same ssd disk but different partitions.

See the attached image of virtualizor admin panel showing incorrect sizes.