Proxmox LVM-Thin proxmox dos 100%

LinuxTec
(usa Debian)

Enviado em 28/10/2022 - 07:35h

Bom dia a todos, utilizo um Proxmox 5.3.5 com um disco de 2TB e nele tenho duas VMS conforme print abaixo em anexo:

Estou enfrentando problemas com local-lvm que seria minha Poll LVM-Thin chegando a 100% e uma das VMS não consegue iniciar.

Alguém saberia me informar como faço para fazer uma limpeza e ganhar espaço, não entendo o porque esta sem espaço as duas vms estão praticamente vazias.

Abaixo segue informações das LVMS do proxmox:

root@proxmoxprincipal:~# vgdisplay
--- Volume group ---
VG Name pve
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 79
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 5
Open LV 4
Max PV 0
Cur PV 1
Act PV 1
VG Size 1.82 TiB
PE Size 4.00 MiB
Total PE 476803
Alloc PE / Size 472708 / 1.80 TiB
Free PE / Size 4095 / 16.00 GiB
VG UUID NU8MgH-917n-AZU5-RzeQ-09Ym-VxQu-IiMSH1

root@proxmoxprincipal:~# lvdisplay
--- Logical volume ---
LV Path /dev/pve/swap
LV Name swap
VG Name pve
LV UUID MjRHrm-n44L-A2vp-8Mcc-TblC-20E4-yWSd9g
LV Write Access read/write
LV Creation host, time proxmox, 2019-03-30 06:42:17 -0300
LV Status available
# open 2
LV Size 8.00 GiB
Current LE 2048
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1

--- Logical volume ---
LV Path /dev/pve/root
LV Name root
VG Name pve
LV UUID 124Lsa-f4CZ-jeZe-1zur-QFTv-VUTY-s9zz31
LV Write Access read/write
LV Creation host, time proxmox, 2019-03-30 06:42:17 -0300
LV Status available
# open 1
LV Size 96.00 GiB
Current LE 24576
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0

--- Logical volume ---
LV Name data
VG Name pve
LV UUID hgPC0D-nnyu-cuAP-8ecw-XiOV-UBsc-Av0esL
LV Write Access read/write
LV Creation host, time proxmox, 2019-03-30 06:42:19 -0300
LV Pool metadata data_tmeta
LV Pool data data_tdata
LV Status available
# open 3
LV Size 1.67 TiB
Allocated pool data 84.82%
Allocated metadata 4.22%
Current LE 437892
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:4

--- Logical volume ---
LV Path /dev/pve/vm-102-disk-0
LV Name vm-102-disk-0
VG Name pve
LV UUID kYCkQM-GIWm-sbDx-I7dM-f6vv-8HKD-m0N7gJ
LV Write Access read/write
LV Creation host, time proxmoxprincipal, 2022-10-27 08:39:06 -0300
LV Pool name data
LV Status available
# open 1
LV Size 1.66 TiB
Mapped size 82.71%
Current LE 435200
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:9

--- Logical volume ---
LV Path /dev/pve/vm-101-disk-0
LV Name vm-101-disk-0
VG Name pve
LV UUID gFhPu2-Scu8-ES7D-244T-LoCY-AINv-12byeM
LV Write Access read/write
LV Creation host, time proxmoxprincipal, 2022-10-28 06:20:13 -0300
LV Pool name data
LV Status available
# open 1
LV Size 50.00 GiB
Mapped size 89.48%
Current LE 12800
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:6

root@proxmoxprincipal:~#
root@proxmoxprincipal:~# lvdisplay
--- Logical volume ---
LV Path /dev/pve/swap
LV Name swap
VG Name pve
LV UUID MjRHrm-n44L-A2vp-8Mcc-TblC-20E4-yWSd9g
LV Write Access read/write
LV Creation host, time proxmox, 2019-03-30 06:42:17 -0300
LV Status available
# open 2
LV Size 8.00 GiB
Current LE 2048
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1

--- Logical volume ---
LV Path /dev/pve/root
LV Name root
VG Name pve
LV UUID 124Lsa-f4CZ-jeZe-1zur-QFTv-VUTY-s9zz31
LV Write Access read/write
LV Creation host, time proxmox, 2019-03-30 06:42:17 -0300
LV Status available
# open 1
LV Size 96.00 GiB
Current LE 24576
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0

--- Logical volume ---
LV Name data
VG Name pve
LV UUID hgPC0D-nnyu-cuAP-8ecw-XiOV-UBsc-Av0esL
LV Write Access read/write
LV Creation host, time proxmox, 2019-03-30 06:42:19 -0300
LV Pool metadata data_tmeta
LV Pool data data_tdata
LV Status available
# open 3
LV Size 1.67 TiB
Allocated pool data 84.82%
Allocated metadata 4.22%
Current LE 437892
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:4

--- Logical volume ---
LV Path /dev/pve/vm-102-disk-0
LV Name vm-102-disk-0
VG Name pve
LV UUID kYCkQM-GIWm-sbDx-I7dM-f6vv-8HKD-m0N7gJ
LV Write Access read/write
LV Creation host, time proxmoxprincipal, 2022-10-27 08:39:06 -0300
LV Pool name data
LV Status available
# open 1
LV Size 1.66 TiB
Mapped size 82.71%
Current LE 435200
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:9

--- Logical volume ---
LV Path /dev/pve/vm-101-disk-0
LV Name vm-101-disk-0
VG Name pve
LV UUID gFhPu2-Scu8-ES7D-244T-LoCY-AINv-12byeM
LV Write Access read/write
LV Creation host, time proxmoxprincipal, 2022-10-28 06:20:13 -0300
LV Pool name data
LV Status available
# open 1
LV Size 50.00 GiB
Mapped size 89.48%
Current LE 12800
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:6


https://prnt.sc/Hcig4vXuNXJQ

DMCbr
(usa Debian)

Enviado em 28/10/2022 - 08:16h

Também enfrento uns problemas por causa disso.
Já reparei que quando volto um backup, algumas VMs voltam com a opção "write zero=1", que faz com que tudo o espaço de disco seja pré-alocado, e outras vem com "write zero=0", ocupando muito pouco espaço. Mas nunca entendi qual é o critério que ele usa pra decidir isso, poderia ter uma opção onde o usuário escolhesse isso.
De qualquer forma, tente clicar no disco virtual da VM e escolher Editar, depois marque a opção Descartar, isso libera um pouco de espaço, mas não muito.

LinuxTec
(usa Debian)

Enviado em 28/10/2022 - 11:34h

Bom dia amigo, obrigado por compartilhar sua experiência, não entendi onde vc diz para selecionar o disco virtual e editar, ao selecionar o disco virtual em Local-lvm não aparece a opção de editar, utilizo a versão Virtual Environment 5.3-5

Tem um camarada que me disse o seguinte veja se isso pra você faz sentido :

"Olá amigo, pelo visto o proxmox não está conseguindo fazer leitura de área dos volumes no storage, tente fazer algum reyscan dos volumes no servidor proxmox"

Você sabe como faz esse reyscan e se pode ser realizado a quente ?