Boas pessoal,
Esta dúvida nao está relacionada directamente com o HA mas estava com esperança de que alguém com experiencia de utilizaçao do proxmox me pudesse ajudar .
Desde há uns dias que o meu proxmox deixou de conseguir contactar com a VM onde tenho o HA instalado. Durante alguns segundos após o arranque ainda consigo fazer login na VM mas rapidamente perde a conexao e após isto acontecer só consigo fazer login directamente no ambiente proxmox com o meu user root, em vez de fazer login directamente na VM .
O proxmox dá indicaçao de um erro (io-error) e tenho o LVM-THIN com indicaçao de 100% usage (o metadata só está a 3%)
Quanto ao disco da VM apenas está com 23% de utilizaçao .
O erro só ocorre após iniciar o boot da VM . Se estiver no menu de arranque ou linha de comandos do grub a conexao à VM mantem-se .
Nao consegui encontrar informaçao relevante no syslog :
Feb 4 14:07:48 proxmox pvedaemon[17870]: <root@pam> starting task UPID:proxmox:000061DB:0188B26B:5E397AB4:qmstart:100:root@pam:
Feb 4 14:07:48 proxmox pvedaemon[25051]: start VM 100: UPID:proxmox:000061DB:0188B26B:5E397AB4:qmstart:100:root@pam:
Feb 4 14:07:48 proxmox systemd[1]: Started 100.scope.
Feb 4 14:07:48 proxmox systemd-udevd[25059]: Using default interface naming scheme 'v240'.
Feb 4 14:07:48 proxmox systemd-udevd[25059]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Feb 4 14:07:48 proxmox systemd-udevd[25059]: Could not generate persistent MAC address for tap100i0: No such file or directory
Feb 4 14:07:49 proxmox kernel: [257356.894291] device tap100i0 entered promiscuous mode
Feb 4 14:07:49 proxmox systemd-udevd[25064]: Using default interface naming scheme 'v240'.
Feb 4 14:07:49 proxmox systemd-udevd[25064]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Feb 4 14:07:49 proxmox systemd-udevd[25064]: Could not generate persistent MAC address for fwbr100i0: No such file or directory
Feb 4 14:07:49 proxmox systemd-udevd[25059]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Feb 4 14:07:49 proxmox systemd-udevd[25059]: Could not generate persistent MAC address for fwpr100p0: No such file or directory
Feb 4 14:07:49 proxmox systemd-udevd[25062]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Feb 4 14:07:49 proxmox systemd-udevd[25062]: Using default interface naming scheme 'v240'.
Feb 4 14:07:49 proxmox systemd-udevd[25062]: Could not generate persistent MAC address for fwln100i0: No such file or directory
Feb 4 14:07:49 proxmox kernel: [257356.984310] fwbr100i0: port 1(fwln100i0) entered blocking state
Feb 4 14:07:49 proxmox kernel: [257356.984315] fwbr100i0: port 1(fwln100i0) entered disabled state
Feb 4 14:07:49 proxmox kernel: [257356.984476] device fwln100i0 entered promiscuous mode
Feb 4 14:07:49 proxmox kernel: [257356.984553] fwbr100i0: port 1(fwln100i0) entered blocking state
Feb 4 14:07:49 proxmox kernel: [257356.984556] fwbr100i0: port 1(fwln100i0) entered forwarding state
Feb 4 14:07:49 proxmox kernel: [257356.996546] vmbr0: port 2(fwpr100p0) entered blocking state
Feb 4 14:07:49 proxmox kernel: [257356.996550] vmbr0: port 2(fwpr100p0) entered disabled state
Feb 4 14:07:49 proxmox kernel: [257356.996715] device fwpr100p0 entered promiscuous mode
Feb 4 14:07:49 proxmox kernel: [257356.996783] vmbr0: port 2(fwpr100p0) entered blocking state
Feb 4 14:07:49 proxmox kernel: [257356.996786] vmbr0: port 2(fwpr100p0) entered forwarding state
Feb 4 14:07:49 proxmox kernel: [257357.008763] fwbr100i0: port 2(tap100i0) entered blocking state
Feb 4 14:07:49 proxmox kernel: [257357.008768] fwbr100i0: port 2(tap100i0) entered disabled state
Feb 4 14:07:49 proxmox kernel: [257357.008982] fwbr100i0: port 2(tap100i0) entered blocking state
Feb 4 14:07:49 proxmox kernel: [257357.008985] fwbr100i0: port 2(tap100i0) entered forwarding state
Feb 4 14:07:50 proxmox pvedaemon[17870]: <root@pam> end task UPID:proxmox:000061DB:0188B26B:5E397AB4:qmstart:100:root@pam: OK
Feb 4 14:08:00 proxmox systemd[1]: Starting Proxmox VE replication runner...
Feb 4 14:08:01 proxmox systemd[1]: pvesr.service: Succeeded.
Feb 4 14:08:01 proxmox systemd[1]: Started Proxmox VE replication runner.
Feb 4 14:08:26 proxmox pvedaemon[17870]: <root@pam> starting task UPID:proxmox:00006273:0188C151:5E397ADA:vncproxy:100:root@pam:
Feb 4 14:08:26 proxmox pvedaemon[25203]: starting vnc proxy UPID:proxmox:00006273:0188C151:5E397ADA:vncproxy:100:root@pam:
Feb 4 14:08:29 proxmox pvedaemon[17870]: <root@pam> end task UPID:proxmox:00006273:0188C151:5E397ADA:vncproxy:100:root@pam: OK
As partiçoes sao estas :
root@proxmox:~# pvs
PV VG Fmt Attr PSize PFree
/dev/sda3 pve lvm2 a-- 55.39g 6.87g
root@proxmox:~# vgs
VG #PV #LV #SN Attr VSize VFree
pve 1 4 0 wz--n- 55.39g 6.87g
root@proxmox:~# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
data pve twi-aotzD- 27.77g 100.00 2.88
root pve -wi-ao---- 13.75g
swap pve -wi-ao---- 5.00g
vm-100-disk-0 pve Vwi-a-tz-- 53.00g data 52.40
root@proxmox:~# dmsetup ls --tree
pve-vm--100--disk--0 (253:6)
└─pve-data-tpool (253:4)
├─pve-data_tdata (253:3)
│ └─ (8:3)
└─pve-data_tmeta (253:2)
└─ (8:3)
pve-swap (253:0)
└─ (8:3)
pve-root (253:1)
└─ (8:3)
pve-data (253:5)
└─pve-data-tpool (253:4)
├─pve-data_tdata (253:3)
│ └─ (8:3)
└─pve-data_tmeta (253:2)
└─ (8:3)
root@proxmox:~#
df -h
Filesystem Size Used Avail Use% Mounted on
udev 2.9G 0 2.9G 0% /dev
tmpfs 580M 38M 543M 7% /run
/dev/mapper/pve-root 14G 2.9G 10G 23% /
tmpfs 2.9G 43M 2.8G 2% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 2.9G 0 2.9G 0% /sys/fs/cgroup
/dev/fuse 30M 16K 30M 1% /etc/pve
tmpfs 580M 0 580M 0% /run/user/0
Alguém tem alguma ideia de como poderei corrigir isto ?
Obrigado