Volume group "pve2" has insufficient free space

[ShaunG]

```
lvcreate 'pve2/vm-101-disk-1' error: Volume group "pve2" has insufficient free space (15950 extents): 115200 required.
```

So, I'm trying to restore from a backup but getting the above error.

PVE2 has plenty of free space: dev/sdb1 pve2 lvm2 a-- <186.31g 86.30g

In fact it's PVE that shows as 96% full.

I remember having some issue before with SSDs and LVM-thin and having to run some command to free up the space, can anyone advise?

 

[fiona]

Hi,
how large are the volumes in the backup? There's a Show Configuration in the backup UI to check this. It sounds like pve2 is used as LVM (rather than LVM-thin). You can use the command lvs to see which logical volumes use up the space.

 

[ShaunG]

@Fabian_E Just coming back to this finally, had some issues with a disk that died.

Output from "lvs":

  LV            VG     Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  data          pve    twi-aotz-- 115.56g             60.04  37.47                           
  root          pve    -wi-ao----  46.50g                                                   
  swap          pve    -wi-ao----   8.00g                                                   
  vm-104-disk-1 pve    Vwi-aotz--  20.00g data        94.06                                 
  vm-105-disk-0 pve    Vwi-aotz--   8.00g data        96.62                                 
  vm-107-disk-1 pve    Vwi-aotz--  16.00g data        36.05                                 
  vm-108-disk-0 pve    Vwi-aotz--  12.00g data        98.85                                 
  vm-109-disk-0 pve    Vwi-aotz--  16.00g data        79.35                                 
  vm-112-disk-0 pve    Vwi-a-tz--  32.00g data        39.12                                 
  vm-100-disk-0 pve2   -wi-ao----   4.00m                                                   
  vm-100-disk-1 pve2   -wi-ao----  32.00g                                                   
  vm-103-disk-1 pve2   -wi-ao----   8.00g                                                   
  vm-106-disk-0 pve2   -wi-ao----  22.00g                                                   
  vm-110-disk-0 pve2   -wi-a-----  38.00g                                                   
  vm-104-disk-0 zmdata -wi-ao---- 800.00g

As you can see PVE2 has lots of space (it's a 200GB drive), and the backup is only 24GB on disk:
rootfs: local-lvm:vm-101-disk-1,size=24G

Any ideas?

 

[ShaunG]

found it! the backup has a 450GB mp0 pointing to another drive, that is no longer there.

is it possible to edit the backup config and remove this line before restore? cannot see anywhere to do it however.

 

[ShaunG]

I cannot find in qmrestore, pct restore or anywhere in the UI a place to change the "configuration" of a vzdump. Surely that's possible ??

 

[fiona]

I cannot find in qmrestore, pct restore or anywhere in the UI a place to change the "configuration" of a vzdump. Surely that's possible ??

Not without manually editing the backup. But you can override the mount structure when using pct restore. See the "advanced" mode described here.

 

[ShaunG]

Not without manually editing the backup. But you can override the mount structure when using pct restore. See the "advanced" mode described here.

The man page doesn't even include this and this page doesn't include the command for mpX? I want to null it out

 

[fiona]

The man page doesn't even include this and this page doesn't include the command for mpX? I want to null it out

Just specify --rootfs without any --mpX options then.
EDIT: For example, pct restore 7777 local:backup/vzdump-lxc-138-2022_04_11-10_52_37.tar --rootfs local-lvm:100 will allocate a 100 GiB volume on local-lvm and restore the container there.

 

[ShaunG]

Just specify --rootfs without any --mpX options then.
EDIT: For example, pct restore 7777 local:backup/vzdump-lxc-138-2022_04_11-10_52_37.tar --rootfs local-lvm:100 will allocate a 100 GiB volume on local-lvm and restore the container there.

Hi, I get this:

tar: ./usr/share/help/es/gnome-terminal/pref-tab-window.page: Cannot create symlink to '': No such file or directory
tar: ./usr/share/help/es/gnome-terminal/pref-custom-command.page: Cannot create symlink to '': No such file or directory
Total bytes read: 1865912320 (1.8GiB, 269MiB/s)
tar: Exiting with failure status due to previous errors

command:

pct restore 101 vzdump-lxc-101-2022_07_03-18_11_07.tar.zst --rootfs local-lvm2:24

 

[fiona]

Hi, I get this:

tar: ./usr/share/help/es/gnome-terminal/pref-tab-window.page: Cannot create symlink to '': No such file or directory
tar: ./usr/share/help/es/gnome-terminal/pref-custom-command.page: Cannot create symlink to '': No such file or directory
Total bytes read: 1865912320 (1.8GiB, 269MiB/s)
tar: Exiting with failure status due to previous errors

Hmm, not sure what these seemingly "empty" symlinks are. There is an --ignore-unpack-errors option which you might want to try.

command:

pct restore 101 vzdump-lxc-101-2022_07_03-18_11_07.tar.zst --rootfs local-lvm2:24