Recent content by itvietnam

Mikrotik is not design for CEPH using. Their software work for routing is good but for heavy load like CEPH is not.

IC. I had followed topic upgrade Proxmox 5.4 to 6.0 with multiple crash because of lib KNET missing. But i still see many crashed report while people using 6.1 do you receive this report too?

it seems corosync 3 is not stable while using knet with unicast (proxmox wiki mentioned unicast support maximum 4 nodes only) from first 8 pages in this box https://forum.proxmox.com/forums/proxmox-ve-installation-and-configuration.16/ we can see many cluster crashed, proxmox reboot/failed...

Update hosts file and point to LAN IP of all node. Then service pvecluster restart

Samsung Evo or Pro is not Enterprise class. They do not support parallel write.

Please search for key word LAG or MLAG. Arista, IBM G8124 support this feature.

Please check your disk speed, it maybe limited by your read speed and write speed.

less than 5 seconds to return this info root@node01:~# pvesh ls nodes/node01/qemu Dr--d 103 Dr--d 213 Dr--d 443 Dr--d 495 Dr--d 513 Dr--d 553 Dr--d 581 Dr--d 655 Dr--d 795 Dr--d 801 Dr--d 803 Dr--d 806 Dr--d...

Hi @udo, it takes few 2 seconds to display: root@node01:~# pvesm status Name Type Status Total Used Available % backup nfs active 46740281344 44594970624 2145310720 95.41% hdd rbd active...

Hi, I have fews cluster: some of them have 3 nodes, some of them have 9 nodes ... all cluster is fast while selecting search box. There is a cluster with 20 nodes, it takes me nearly 1 minute to show things up. May i know how to investigate this root cause Our pveversion: proxmox-ve: 6.1-2...

Hi @spirit, do you see any delay while you type any VMID in Proxmox search box from your cluster 20 nodes?

Please try to install from epel repo, then they will included cloud-init 18.2

Hi, I have 10 node named from node1 to node10. I have shutdown node9 for maintenance. Then i removed node2 by pvecm delnode node2 Later i turn on node9 back and whole system shutdown (reboot random). It seems something fence all nodes. May i know how to turn on node9 back to the system...

can we do rolling update by migrate VPS to other node and keep it online or we have to force shutdown all VPSes before doing upgrade? I could see corosync v3 has a lot of issues here: https://forum.proxmox.com/threads/pve-5-4-11-corosync-3-x-major-issues.56124/ so is it stable now?

since proxmox v6 used corosync 3 so is it stable for proxmox v6 now?