Recent content by efg

I am basing this on the following: The post says that memory leaks during smb dump. I have it without any additional actions. Also, it says that the problem appeared when I switched to kernel 6.8, but this problem started when I switched from pve 7.5 to pve 8.1.4 (Linux kernel 6.5.13-1-pve).

I checked, CIFS Storage is not used for dumps. All backups are put on pbs. I guess that's not my case

vms - 32G + 4G Arc - 32G But at the same time, Used - 181G

root@proxmox-sd07:~# uname -a Linux proxmox-sd07 6.8.8-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.8-1 (2024-06-10T11:42Z) x86_64 GNU/Linux I have storage cifs connected in a pve cluster. Sometimes used for backing up virtual machines cifs: VEEAM01 path /mnt/pve/VEEAM01 server...

I had to reboot the original server, but I found another server with a similar problem. root@proxmox-sd07:~# free -h total used free shared buff/cache available Mem: 503Gi 181Gi 21Gi 72Mi 304Gi 321Gi Swap...

I tried to perform this now, but it had no effect unfortunately.

Hi! Some servers in my cluster are experiencing unrelated RAM consumption. For example there is a host running two kvm with 120GB dedicated memory + zfs arc 16GB. But at the same time the memory consumed by the host is 468GB. 468 - 120 -120 - 16 = 212 What can another 212GB be used for...

@Spirog After hetzner removed the traffic limit, my problem was solved by turning off one of the servers completely and turning it back on :) ! I would like to report on the probable causes of the destruction of the cluster. When the cluster collapsed, all cluster nodes were up and available...

pveversion -v proxmox-ve: 7.1-1 (running kernel: 5.13.19-3-pve) pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe) pve-kernel-helper: 7.1-8 pve-kernel-5.13: 7.1-6 pve-kernel-5.4: 6.4-12 pve-kernel-5.13.19-3-pve: 5.13.19-7 pve-kernel-5.4.162-1-pve: 5.4.162-2 ceph-fuse: 14.2.21-1 corosync...

Spirog, thank you very much. It's great to have someone to help:).

I'm afraid to turn off all nodes, because now VMs are running on the remaining nodes, and if the quorum is not met after restarting the nodes, the VMs will not start. Maybe there is a safer way?

I only have 10 nodes cat /etc/corosync/corosync.conf logging { debug: on to_syslog: yes } nodelist { node { name: staging nodeid: 3 quorum_votes: 1 ring0_addr: 136.243.39.81 } node { name: x3 nodeid: 10 quorum_votes: 1 ring0_addr: 95.216.17.92 }...

It did not help. I am getting error Unable to set expected votes: CS_ERR_INVALID_PARAM

Please help. Cluster stopped working. After rebooting the server vm does not start. From the console, too, it is not possible to launch them. pvecm status Cluster information ------------------- Name: asodesk Config Version: 52 Transport: knet Secure auth: on Quorum...