Search results

Hi, same here wiht one cluster node only and ceph: proxmox-ve: 6.0-2 (running kernel: 5.0.21-1-pve) pve-manager: 6.0-6 (running version: 6.0-6/c71f879f) pve-kernel-5.0: 6.0-7 pve-kernel-helper: 6.0-7 pve-kernel-4.15: 5.4-6 pve-kernel-5.0.21-1-pve: 5.0.21-1 pve-kernel-5.0.18-1-pve: 5.0.18-3...

I've restarted all nodes since the upgrade to 6 versions at leat two times, in the other cluster too, no changes in monitor's latency i'm afraid. Regards

Just in case someone it's interested I've already builded the new cluster with Supermicro servers and can confirm performance it's normal. I had no way to know exactly what happened with Dell R620, tried to open a support case with Dell but they only support through support forums, I do not use...

Hi Alwin, how can I check that? I do not see any error on mon logs, just rocksdb entries and latency histograms. All disks are enterprise ssds. Can't tell if fstrim is needed, but latency increase was right after the update in all three different clusters. root@int101:/var/log/ceph# fstrim...

Hello Alwin. I've restarted monitors with no changes. https://pastebin.com/raw/cDGkvJAD

Hello Alwin, nope, just monitors.

Hi, I've noticed monitor latency skyrocket after update in all my clusters. Any way to check why or how to improove/fix it? Config is the same in the three nodes. I've noticed this latency increase in three different clusters: # pveversion --verbose proxmox-ve: 6.0-2 (running kernel...

Hi, can staff please comment on https://forum.proxmox.com/threads/proxmox-ve-6-0-released.56001/page-5#post-258835. ? I guess shoul be any impact on such latency increase, but I do not notice any so far. Thanks

Hi, I've noticed monitor latency skyrocket after update in all my clusters. Any way to check why or how to improove/fix it? Regards

Thanks for replying. I know it's not exactly same hardware, disks are the same, ceph config it's the same, cpu's and network are also the same. I know mbs and controllers are different, but SAS3008 are in the slow one. I've started in the new/slowest cluster using PERC Controller but...

I've checked Individual latency for one disk in one node of each cluster and I'm notable to see such 10X difference in latency with ioping

No ideas? I was thinking in backplane, but I do not know how to test that. Any R620 based cluster outthere to compare latency metrics? Regards

Hi, we've been using proxmox ceph cluster for a year in one datacenter and decided to build a new one in another one recently, but we are unable to get the first one performance with the new one, in fact we have a 10X latency in the new one with a few VMs running for one hundred in the old one...

Hi, I've seen you can set freeze on global HA options shutdown policy in 5.4. Is possible to set this per vm? I'm interested in freeze some of the vms only on shutdown, but not all vms. Regards

No, I've tried that too. I've even see the disk in the nfs share content from gui created before the timeout lock when creating a 1 Tb vm disk, when error shows up the disk is deleted from nfs. Regards

Hi Astraea, thnaks for reply. Yes, I've updated and restarted all nodes. Regards

Hi, I got this error: create full clone of drive scsi0 (ceph-vm:vm-108-disk-0) TASK ERROR: storage migration failed: error with cfs lock 'storage-nfsvms': unable to create image: got lock timeout - aborting command I've searched forum and only found a thread regarding quorum issues, not the...

Thanks Thomas, that added the right entry to the known hosts. Regards

Thanks for the detailed answer Thomas, but pvecm updatecerts did not solved the issue, on all nodes: root@int102:~# pvecm updatecerts root@int102:~# /usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=int103' root@10.10.10.103 /bin/true Host key verification failed. root@int102:~# ssh -o...

I've seen other post related to this issue but I cannot see any clear solution. root@int102:~# /usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=int103' root@10.10.10.103 /bin/true Host key verification failed. root@int102:~# ssh 10.10.10.103 Linux int103 4.13.13-6-pve #1 SMP PVE...