Recent content by divelgrom

  1. D

    Add disk creation functionality when using lvm storage

    When using lvm as virtual disk storage it is not enough to pass additional parameters for lvm Example use in console: lvcreate -n vmid-disk-0 --type striped -L 32G -i 4 vg In VG can have e.g. 4 disks (or another number), and the final LV can be created with different parameters, for different...
  2. D

    Error bootload PV

    current version: pve-manager/5.1-36/131401db (running kernel: 4.10.8-1-pve) The problem lies in the 4.13.8-2-pve kernel version. Boot is stoped on initramfs. No block devices. After downgrade to 4.10 the system boots normally.
  3. D

    pveproxy become blocked state and cannot be killed

    Maybe this is a coincidence for after I have disabled NFS from all nodes. Pveproxy began to work more stable.
  4. D

    pveproxy become blocked state and cannot be killed

    This solution does not help for long. Today on 3 nodes again broke the pveproxy process. And restarting pveproxy without rebooting pve-cluster is impossible In what there can be a reason of such behavior?
  5. D

    pveproxy become blocked state and cannot be killed

    Good day. I managed to cope with the problem. Using the following commands. # systemctl restart pve-cluster.service # pvecm updatecerts -f # systemctl restart pveproxy.service Strange situation. Old certificates were valid until 2025. After pvecm updatecerts -f Pveproxy started and...
  6. D

    pveproxy become blocked state and cannot be killed

    # ps faxl | awk '$10~"D" {print $0}' 4 0 30942 30941 20 0 19260 3768 iterat D ? 0:00 \_ git add . 4 0 84839 1 20 0 239688 66060 filena Ds ? 0:00 /usr/bin/perl -T /usr/bin/pveproxy start # dmesg | grep "blocked for more than 120...
  7. D

    pveproxy become blocked state and cannot be killed

    Under the system I have installed a mechanical hard drives. Below I tried to start pveproxy and followed the recommendations. # free -h total used free shared buffers cached Mem: 314G 196G 118G 4.2G 390M 5.6G -/+...
  8. D

    pveproxy become blocked state and cannot be killed

    At the moment swap out activity. procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu----- r b swpd free buff cache si so bi bo in cs us sy id wa st 14 0 15709016 36706880 198028 1721140 0 0 473 434 0 0 7 2 91 0 0 10 1...
  9. D

    pveproxy become blocked state and cannot be killed

    Nfs share is there but it is available. pvesm status WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it! hetzner_backup_0 nfs 1 10735915008 86672384 10649226240 1.31% local dir 1 163036644 21889292 141130968 13.93%...
  10. D

    pveproxy become blocked state and cannot be killed

    Good afternoon. I ran into the same problem. I have a cluster of 4 servers. On 3 of 4 pveproxy does not work, hangs in the "Ds" state. root 34194 0.0 0.0 239612 66012 ? Ds 11:44 0:00 /usr/bin/perl -T /usr/bin/pveproxy start # pveversion -v proxmox-ve: 4.4-84 (running kernel...
  11. D

    [SOLVED] Backup VM on NFS.

    As it turned out the problem is observed only with one virtual machine. Others can be backuped normally
  12. D

    [SOLVED] Backup VM on NFS.

    Okey. I'll try, and the result will inform
  13. D

    [SOLVED] Backup VM on NFS.

    Hello. I have the following situation: There are 2 Proxmox node in different countries. Between them built ipip tunnel. Node A - Role: Active - NFS client - pve-manager/4.4-13/7ea56165 (running kernel: 4.4.49-1-pve) Node B - Role: Backup\Standby - NFS server - pve-manager/4.4-13/7ea56165...